mcp-registry/io.github.carrasquelalex1/hipocampo · v1.30.0
As of 2026-10-27 01:45 UTC, the Carrasquelalex1 Hipocampo MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 8 minutes.
Bilingual dual memory with SSC for AI agents. Semantic search, embeddings, profiles.
Point your MCP client at this streamable-http endpoint: https://alexbell1-hipocampo-mcp.hf.space/mcp
40 of 40 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 →
111 parameter(s) across 32 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 →
4 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 →
In the last 30 days: 0 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 32 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.carrasquelalex1%2Fhipocampo/fixes
{
"name": "add_watch_dir",
"description": "Agrega un directorio al watch list para auto-reindexación.",
"inputSchema": {
"type": "object",
"title": "add_watch_dirArguments",
"required": [
"path"
],
"properties": {
"path": {
"type": "string",
"title": "Path"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "delete_hipocampo",
"description": "\n Elimina un recuerdo del Hipocampo (memoria_vectorial) por su ID.\n\n Esta operación es irreversible. Una vez eliminado, el recuerdo\n no podrá recuperarse ni aparecerá en búsquedas futuras.\n\n Args:\n id: ID numérico del recuerdo a eliminar.\n\n Returns:\n Confirmación de eliminación.\n ",
"inputSchema": {
"type": "object",
"title": "delete_hipocampoArguments",
"required": [
"id"
],
"properties": {
"id": {
"type": "integer",
"title": "Id"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "get_hipocampo",
"description": "Obtiene una memoria exacta por ID, sin pasar por el ranking.\n\n Acepta el ID numérico de memoria_vectorial (4039), con prefijo (#4039,\n v4039) o el ID de memory_items (vmi<uuid>). Es la vía determinista para\n \"tráeme el recuerdo N\": no compite con decenas de resultados.\n\n Args:\n id: ID de la memoria (numérico o vmi<uuid>).\n format: \"compact\" (default), \"full\" o \"json\".\n\n Returns:\n La memoria completa (compact muestra un fragmento de 800 chars;\n full/json",
"inputSchema": {
"type": "object",
"title": "get_hipocampoArguments",
"required": [
"id"
],
"properties": {
"id": {
"type": "string",
"title": "Id"
},
"format": {
"type": "string",
"title": "Format",
"default": "compact"
}
}
},
"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.carrasquelalex1/hipocampo"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.carrasquelalex1/hipocampo"}) over MCP.
search_hipocampo ~548 tokensquick_hipocampo_search ~487 tokenssave_hipocampo ~396 tokensupdate_hipocampo ~335 tokenscompress_hipocampo ~289 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.carrasquelalex1%2Fhipocampo?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.carrasquelalex1%2Fhipocampo?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.carrasquelalex1%2Fhipocampo.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.carrasquelalex1%2Fhipocampo.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.carrasquelalex1%2Fhipocampo?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:60043648ecfdb308…, first seen 2026-10-20, included at leaf 34789 of 76,667. Version history · verify what your client received.
Compare: most reliable files servers · most reliable data servers · most reliable knowledge servers · most reliable database servers · most reliable retrieval 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 01:45 UTC, the Carrasquelalex1 Hipocampo MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 8 minutes.
Carrasquelalex1 Hipocampo MCP server advertises 40 tools, including add_watch_dir, compress_hipocampo, consolidate_hipocampo, contradicciones_hipocampo, decay_hipocampo.
Point your MCP client at this streamable-http endpoint: https://alexbell1-hipocampo-mcp.hf.space/mcp
Glimind scanned all 40 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.