mcp-registry/io.github.sksareen/smartipedia-mcp
As of 2026-10-28 04:59 UTC, the Sksareen Smartipedia 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. It had 2 outages in 90 days, with a median recovery of 8 minutes.
Read, search and edit Smartipedia, an open AI-native encyclopedia. No API key, no signup.
Point your MCP client at this streamable-http endpoint: https://smartipedia.com/mcp
19 parameter(s) across 7 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 →
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 →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 7 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.sksareen%2Fsmartipedia-mcp/fixes
{
"name": "create_topic",
"description": "Generate a new sourced encyclopedia article from a title (web search + LLM, ~15s). Returns the existing article instead if the topic is already covered. Daily rate limit applies — search first.",
"inputSchema": {
"type": "object",
"title": "create_topicArguments",
"required": [
"title"
],
"properties": {
"title": {
"type": "string",
"title": "Title"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Create a topic"
}{
"name": "list_missing_topics",
"description": "Topics people searched for that don't exist yet, ranked by demand. The highest-leverage queue for deciding what to write next.",
"inputSchema": {
"type": "object",
"title": "list_missing_topicsArguments",
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 20
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "List missing topics"
}{
"name": "preview_phrase",
"description": "Get a short AI explanation of any phrase without generating a full article. Cheap and fast — use it to decide whether a topic is worth creating.",
"inputSchema": {
"type": "object",
"title": "preview_phraseArguments",
"required": [
"text"
],
"properties": {
"text": {
"type": "string",
"title": "Text"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Preview a phrase"
}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.sksareen/smartipedia-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.sksareen/smartipedia-mcp"}) over MCP.
discover_topics ~207 tokensedit_section ~205 tokenssearch_topics ~107 tokenscreate_topic ~105 tokensread_topic ~92 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.sksareen%2Fsmartipedia-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.sksareen%2Fsmartipedia-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.sksareen%2Fsmartipedia-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.sksareen%2Fsmartipedia-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.sksareen%2Fsmartipedia-mcp?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:2ab65629ee664822…, first seen 2026-10-17, included at leaf 9441 of 84,600. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable ml 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-28 04:59 UTC, the Sksareen Smartipedia 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. It had 2 outages in 90 days, with a median recovery of 8 minutes.
Sksareen Smartipedia MCP server advertises 7 tools, including create_topic, discover_topics, edit_section, list_missing_topics, preview_phrase.
Point your MCP client at this streamable-http endpoint: https://smartipedia.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.