mcp-registry/com.valksor/hub · v2.1.0
As of 2026-10-23 07:50 UTC, the Valksor Hub MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 54 outages in 90 days, with a median recovery of 2 minutes.
One MCP endpoint over every Valksor dictionary: namespaced tools plus a JSON passthrough.
Claude Code
claude mcp add --transport http valksor-hub-mcp-server https://mcp.valksor.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"valksor-hub-mcp-server": {
"type": "http",
"url": "https://mcp.valksor.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
In the last 30 days: 36 tool(s) removed and 8 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 →
2 tools share an identical description with another tool on this server.
Make each description say how the tool differs from its siblings, or the model will pick between them at random. How to fix →
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.valksor/hub"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.valksor/hub"}) over MCP.
livonian_search ~871 tokensinterslavic_search ~860 tokensanglo_search ~810 tokensslavonic_search ~805 tokensscythian_search ~793 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.valksor%2Fhub?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.valksor%2Fhub?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.valksor%2Fhub.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.valksor%2Fhub.svg :target: https://glimind.com/server/mcp-registry%2Fcom.valksor%2Fhub?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:801bfb3ef9f3a016…, first seen 2026-10-23, included at leaf 48985 of 50,871. Version history · verify what your client received.
Compare: most reliable other servers · most reliable data servers · most reliable search 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-23 07:50 UTC, the Valksor Hub MCP server is up with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 54 outages in 90 days, with a median recovery of 2 minutes.
Valksor Hub MCP server advertises 27 tools, including anglo_deromanize, anglo_get_inflections, anglo_romanize, anglo_search, dictionaries.
Point your MCP client at this streamable-http endpoint: https://mcp.valksor.com/mcp
Glimind scanned all 27 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.