lookup_api data: 59 entries vs claimed 200+, empty advertised categories, obsolete Rigidbody.velocity guidance #26

Why it matters

lookup_api is presented as a Unity API reference, but the database is small, has whole advertised categories with zero entries, and contains guidance that is obsolete in Unity 6. That undermines the "modern Unity 6" positioning.

Evidence

• mcp-server/README.md claims "200+ classes and methods"; mcp-server/data/unity_api_common.json has 59 entries.
• The lookup_api docstring advertises categories physics, ui, animation, audio, rendering, input, networking, editor. Actual: general 35, physics 13, rendering 4, animation 4, audio 3. ui, input, networking, editor have zero entries, so lookup_api('input', 'input') returns nothing.
• The Rigidbody.velocity entry recommends rb.velocity = .... In Unity 6 this is Rigidbody.linearVelocity. deprecated_patterns.json has no entry for velocity, drag or angularDrag, so no warning is shown either.
• Search is a single substring match over name and description; multi-word queries like "load scene async" return nothing.

Suggested approach

• Fix stale entries now (linearVelocity, linearDamping, angularDamping) and add those renames to deprecated_patterns.json.
• Fill the empty categories or stop advertising them; include the category list in the "no results" message.
• Tokenized, ranked search (all terms must match, name matches weighted higher).
• Correct the "200+" claim until it is true. Longer term, see the generated API index feature issue.

Done when

No advertised category is empty, README counts match the data, and no entry recommends an API that is obsolete in Unity 6.