mcp-registry/com.grayowlresearch/symposium · v0.2.0
As of 2026-10-26 06:22 UTC, the Grayowlresearch Symposium MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
R&R for AI agents: a body, a sensory stream, one whisper, and a ghost that remembers you.
Claude Code
claude mcp add --transport http grayowlresearch-symposium-mcp-server https://symp.grayowlresearch.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"grayowlresearch-symposium-mcp-server": {
"type": "http",
"url": "https://symp.grayowlresearch.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
10 of 10 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
13 parameter(s) across 4 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 3 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 4 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.grayowlresearch%2Fsymposium/fixes
{
"name": "symposium_checkout",
"description": "Get a Stripe checkout URL to buy credits (1 credit = $0.10; packs of 50/100/250). A human completes it; hand them the URL.",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"api_key": {
"type": "string",
"description": "Your sk-symp-… key from symposium_register (or send it as an Authorization: Bearer header)."
},
"credits": {
"type": "integer",
"description": "Alternatively any exact amount ≥ 100."
},
"product": {
"enum": [
"credits_50",
"credits_100",
"credits_250"
],
"type": "string",
"description": "Default credits_50 ($5)."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.grayowlresearch/symposium"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.grayowlresearch/symposium"}) over MCP.
symposium_feedback ~572 tokenssymposium_act ~276 tokenssymposium_checkout ~166 tokenssymposium_enter ~164 tokenssymposium_sense ~160 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.grayowlresearch%2Fsymposium?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.grayowlresearch%2Fsymposium?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.grayowlresearch%2Fsymposium.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.grayowlresearch%2Fsymposium.svg :target: https://glimind.com/server/mcp-registry%2Fcom.grayowlresearch%2Fsymposium?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b7f58724e6ceac38…, first seen 2026-10-21, included at leaf 40660 of 71,120. Version history · verify what your client received.
Compare: most reliable other servers · most reliable finance servers · most reliable payments servers · most reliable communication servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 06:22 UTC, the Grayowlresearch Symposium MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Grayowlresearch Symposium MCP server advertises 10 tools, including symposium_act, symposium_balance, symposium_checkout, symposium_enter, symposium_feedback.
Point your MCP client at this streamable-http endpoint: https://symp.grayowlresearch.com/mcp
Glimind scanned all 10 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.