registry / record
exa-mcp-server
> throne registry exa-mcp-server
sealed
- scan id
- 8de0046ba07445f782ddf4beb57fabb8
- target
- exa-mcp-server
- sealed at
- 2026-06-12 06:50:05Z
- evidence hash
- sha256:a04e5568d5318a296ce3b5ffcce1213de3439332f8b5a47e158e858eec46d16d
initialize ok: server exa-search-server 3.2.1, negotiated protocolVersion 2025-11-25, capabilities ['completions', 'prompts', 'resources', 'tools']
supported: tools/list (2 tools), resources/list (1), prompts/list (1)
all 2 tool inputSchemas are valid JSON Schema
called 2 of 2 tools (cap 10): 0 ok, 2 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived — wrong_type_args: accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive
no streaming-capable tool declared by this server; not applicable (pass-na)
read exa://tools/list (1 content blocks); subscribe capability not declared (pass-na)
ladder 1/2/4/8 overlapping web_search_exa calls: max_observed_stable_concurrency=8; all ids answered exactly once, but every call returned an error (tool-level isError result) — the tool may need runtime dependencies this sandbox does not provide
transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)
initialize ok: server exa-search-server 3.2.1, negotiated protocolVersion 2025-11-25, capabilities ['completions', 'prompts', 'resources', 'tools']
supported: tools/list (2 tools), resources/list (1), prompts/list (1)
all 2 tool inputSchemas are valid JSON Schema
called 2 of 2 tools (cap 10): 0 ok, 2 returned tool-level errors (expected for synthesized args)
structured error responses, connection survived — wrong_type_args: accepted (returned result); unknown_method: error(-32601); invalid_id: no response (silent), connection alive
no streaming-capable tool declared by this server; not applicable (pass-na)
read exa://tools/list (1 content blocks); subscribe capability not declared (pass-na)
ladder 1/2/4/8 overlapping web_search_exa calls: max_observed_stable_concurrency=8; all ids answered exactly once, but every call returned an error (tool-level isError result) — the tool may need runtime dependencies this sandbox does not provide
transport closed and relaunched; re-handshake ok (protocolVersion 2025-11-25, first session was 2025-11-25)
"prepare" runs on git-dependency installs and local dev (not registry installs): 'npm run build:stdio'
package/package.json8 non-local endpoint host(s) referenced in code — verify each is expected for this server's purpose: api.agnost.ai (package/smithery/stdio/index.cjs:75), api.exa.ai (package/smithery/stdio/index.cjs:80), dashboard.exa.ai (package/smithery/stdio/index.cjs:88), lodash.com (package/smithery/stdio/index.cjs:214), mcp.exa.ai (package/smithery/stdio/index.cjs:88), npms.io (package/smithery/stdio/index.cjs:19), openjsf.org (package/smithery/stdio/index.cjs:215), underscorejs.org (package/smithery/stdio/index.cjs:217)
package/smithery/stdio/index.cjs:19obsolete protocol version string '2024-10-07' in source
package/smithery/stdio/index.cjs:65obsolete protocol version string '2024-11-05' in source
package/smithery/stdio/index.cjs:65paste this in your README. it renders the live verdict and links back to this record. if a release ever breaks the verdict, the badge says so on its own.
[](https://usethrone.dev/server/exa-mcp-server)maintainer of this server? challenge this record: hello@usethrone.dev. tell us what we got wrong and we re-run it in the open.
this page renders the stored record of a real run. nothing on it is asserted without the execution that proved it.