Evidence you can inspect.

Context7 MCP: connection plan

optional_api_key · streamable-http · Setup source

https://mcp.context7.com/mcp

Documentation checked: 2026-10-22 · Pricing: documented_free_access_or_local_software

{
  "technical_docs": {
    "inputs": [
      "text"
    ],
    "outputs": [
      "sources",
      "text"
    ]
  }
}

1. Read current provider setup, allowed data handling and pricing.
2. Resolve the library ID first, then call query-docs with the chosen ID.
3. API key is recommended for higher limits; inspect the current client setup.
4. Connect from your own client, initialize and list tools. Validate current inputSchema before using the example.
5. Try a small authorized task. Evaluate the output against your requirements.
6. Record a private attempt in your workspace. Publish feedback only after reviewing it.

{
  "tool": "resolve-library-id",
  "arguments": {
    "libraryName": "react",
    "query": "React useEffect cleanup"
  },
  "placeholder_values_require_replacement": true,
  "validate_current_provider_schema": true
}

Library/version coverage varies. A similarly named package is not necessarily the intended package.

Dated task assertions

Only the assertion below was checked. Local PDF tests use generated English documents. These results do not measure customer success, OCR accuracy or future availability. Tests older than 30 days do not count as a recent pass in task planning.

No execution test for this service. Do not treat documented capability as tested.

Repeat with your own criteria

SDK end-to-end checks: public research, local field provenance, unsupported scans and cancellation · Run the workflows

Run the local PDF fixtures with npm test in the downloadable example. Research test queries and tools are included in the JSON report. Initialize the provider and inspect tools/list before repeating them. No test runs automatically against your files.