MCP Connector Lint
Checks an MCP connector manifest, tool annotations and directory listing text against the Claude Connectors Directory requirements.
It is a remote MCP server with three read-only tools. No account, no OAuth, no data retained.
Point a custom connector at https://mcp-lint.superintelligencesystems.ca/mcp.
Tools
| Tool | What it returns |
|---|---|
validate_manifest | A JSON report on the connector manifest: transport, HTTPS URL, auth mode, first-party service domain, and every tool's annotations. |
check_tool_annotations | A JSON report on a tools/list array: titles, hints, name length and format, unique names, input schemas, description hygiene. |
lint_listing_text | A JSON report on a listing draft: published character limits, categories, docs/privacy URLs, support contact, reviewer note, copy rules. |
All three are read-only, deterministic and authless. Findings carry a stable rule id, a severity, the field path and a fix; blocking errors fail the check, warnings do not.
Call it
curl -s https://mcp-lint.superintelligencesystems.ca/api/v1/validate-manifest \
-H 'content-type: application/json' \
-d '{"manifest":{"name":"Example","url":"https://api.example.com/mcp","transport":"streamable-http","authentication":"none","service_domain":"example.com","tools":[{"name":"get_weather","title":"Get weather","description":"Returns the current weather for one city.","readOnlyHint":true,"inputSchema":{"type":"object","properties":{}}}]}}'
REST responses and MCP tool results are the same JSON. See the documentation for the full rule set and the rules endpoint for the machine-readable catalogue.
What it does not do
- It does not connect to your server, call your tools or fetch your docs, privacy or icon URLs. Static text and structure only.
- It does not submit, score or approve a directory listing. Passing this check does not imply directory approval.
- It stores nothing: each request is processed in memory and the result is returned.