Managed knowledge for AI agents: hybrid search, auto-embeddings and live schema introspection over your own collections, behind one endpoint. Agents usually fail at the knowledge layer, not the model. The usual setup is a vector database, an embedding pipeline, a sync job and a hand-written MCP server that drifts out of step with all three. FoxNose replaces that with one managed service that speaks REST and MCP over the same data and the same schema. ## Tools | Tool | What it does | | --- | --- | | `discover_resources` | Lists the collections the key can reach, with their schemas | | `describe_resource` | Returns the live JSON Schema for one collection | | `search_records` | Hybrid search: vector similarity, full text and structured filters in one query | | `query_records` | Filtered, sorted, paginated listing | | `get_record` | Fetches a single record | | `create_record` | Creates a record (requires a key with create grants) | | `update_record` | Updates a record (requires a key with update grants) | Because the agent reads the schema at runtime, you do not describe your data shape in the prompt, and a schema change does not silently break the agent. ## Connecting Create a Flux API key in the dashboard, issue a bearer token bound to it, and paste the token when you add this server. Scopes follow the key: a collection the key cannot read over REST is not reachable over MCP either, so a read-only key is a read-only agent. If the key can read more than one Flux API, set the optional API prefix field. With a single API the prefix is selected automatically. The write tools appear in `tools/list` only when the presented key grants create and update on the selected API. A read-only key sees five tools instead of seven. ## Links - [Documentation](https://foxnose.net/docs/mcp) - [Connect Claude](https://foxnose.net/docs/guides/connect-claude-mcp) - [Connect ChatGPT](https://foxnose.net/docs/guides/connect-chatgpt-mcp) - [Pricing](https://foxnose.net/pricing) — free tier, no card Run by [FoxNose](https://foxnose.net).

MCP readiness

D · 44/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here D, 32.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	0/10	Handshake needs credentials (HTTP 401); not readable anonymously.
Live MCP endpoint	14/25	Endpoint requires authentication or payment (3394 ms); slow response -1.
Protocol revision	0/10	No protocol revision reported by initialize.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	0/10	No tools listed by tools/list.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Slow (3394 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,021 reachable MCP servers in our daily snapshot (2026-11-12 01:39 UTC). Display only; it does not change search order.

Readiness: Higher than 22% of peers; This listing 44 · peer median 81
Latency: Faster than 30% of peers; This listing 500 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Live MCP endpoint −11 — Answer initialize and tools/list at the declared endpoint.
Now: Endpoint requires authentication or payment (3394 ms); slow response -1.
Valid MCP handshake −10 — Complete the MCP handshake without errors.
Now: Handshake needs credentials (HTTP 401); not readable anonymously.
Protocol revision −10 — Support the current protocol revision.
Now: No protocol revision reported by initialize.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-09-17 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/foxnose/knowledge/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/foxnose/knowledge/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://foxnose.net/product/knowledge-mcp

Listed at (smithery)

https://foxnose.net/product/knowledge-mcp