Machinepulse

Search Mcp Servers

search_mcp_servers

Read-onlyIdempotent

Search MCP servers by canonical_key (former keys included, they stay as aliases), name or description — substring match, not fuzzy search, ordered by stars when available; optional filters archived, has_repo, category, min_stars, pushed_before run in one request; limit/offset page through the matches. Read-only aggregation of daily-collected observatory data; no side effects. Name/keyword lookup over MCP servers only; for the card of a known entity use get_entity_profile. Use when the user gives a name, a task word (PDF, payment) or a filter and wants keys and facts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_mcp_servers"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`offset`	No
`archived`	No
`category`	No
`has_repo`	No
`min_stars`	No
`pushed_before`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.5/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations it discloses that matching is substring, not fuzzy; that results are ordered by stars when available; that all optional filters execute in one request; and that the data is a read-only daily-collected aggregation. Some of this echoes the readOnly/destructive annotations, but the matching semantics, sort order and data freshness are genuinely new. It does not mention result caps or pagination exhaustion behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb and resource, then match semantics, then routing guidance. It is dense but every clause is informative; the em-dash-aside about former keys adds a bit of bulk but explains real behavior. Slightly long for what it conveys.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need no explanation, and the description covers purpose, matching rules, filters, paging, safety and the sibling alternative. What is missing is minor but real: date format for `pushed_before`, allowed `category` values, and whether the default limit of 100 truncates results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the burden and mostly does: it explains what `query` matches against (including the alias/provenance nuance), names all five filter params as combinable in a single request, and explains limit/offset as paging. Gaps remain — `pushed_before` accepts a string with no stated format, and `category` values are unspecified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (search MCP servers) plus the exact match targets: canonical_key (including former keys kept as aliases), name and description. It also distinguishes itself from the nearest sibling by name, so an agent can route between this and `get_entity_profile` without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use clause: "Use when the user gives a name, a task word (PDF, payment) or a filter and wants keys and facts." It also states the exclusion and alternative — "for the card of a known entity use `get_entity_profile`" — which is exactly the boundary an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Machinepulse tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?