mcp-registry/io.github.tensorswillflow/verbaterm · v1.0.0
As of 2026-10-27 05:11 UTC, the Tensorswillflow Verbaterm MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 3 minutes.
Judged, citation-checked policy corpus over MCP. Keyless public reads; API key for AI tools.
Point your MCP client at this streamable-http endpoint: https://verbaterm.com/mcp
7 of 7 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 →
5 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 →
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%2Fio.github.tensorswillflow%2Fverbaterm/fixes
{
"name": "get_policy_review",
"description": "Get the full judged review for one published policy: findings with verbatim citation excerpts, scores, summary, and provenance. Cite the source URLs back to the user.",
"inputSchema": {
"type": "object",
"required": [
"companySlug",
"productSlug",
"policyKind"
],
"properties": {
"policyKind": {
"type": "string",
"description": "terms, privacy, cookies, data_processing, or other."
},
"companySlug": {
"type": "string"
},
"productSlug": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_private_review_progress",
"description": "Poll progress of a private review started with start_private_review.",
"inputSchema": {
"type": "object",
"required": [
"sessionId"
],
"properties": {
"sessionId": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_private_review_result",
"description": "Get the completed private review (findings + citations) for a session started with start_private_review. Raw source text is not returned.",
"inputSchema": {
"type": "object",
"required": [
"sessionId"
],
"properties": {
"sessionId": {
"type": "string"
}
}
},
"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/io.github.tensorswillflow/verbaterm"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.tensorswillflow/verbaterm"}) over MCP.
start_private_review ~153 tokenssearch_policies ~143 tokensask_question ~139 tokensget_policy_review ~132 tokensget_private_review_result ~82 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%2Fio.github.tensorswillflow%2Fverbaterm?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.tensorswillflow%2Fverbaterm?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.tensorswillflow%2Fverbaterm.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.tensorswillflow%2Fverbaterm.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.tensorswillflow%2Fverbaterm?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:6116f7396f1a4e03…, first seen 2026-10-17, included at leaf 1388 of 77,542. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable retrieval servers · most reliable productivity servers · most reliable data servers · most reliable search 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-27 05:11 UTC, the Tensorswillflow Verbaterm MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 3 minutes.
Tensorswillflow Verbaterm MCP server advertises 7 tools, including ask_question, get_policy_review, get_private_review_progress, get_private_review_result, list_policies.
Point your MCP client at this streamable-http endpoint: https://verbaterm.com/mcp
Glimind scanned all 7 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.