A
licenseB
qualityA
maintenanceYour portable AI memory layer. Classify, store, and recall what matters across models, tools, and devices.
31
5
MIT
anamnese
Server Details
A self-improving memory layer. Your memory, notes, tasks and goals, remembered everywhere.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- OAuth
- Not checked
- Last Tested
- Transport
- Streamable HTTP
- URL
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user or an account that owns the GitHub organization, then choose Claim with GitHub.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
AI memory layer — one shared, persistent memory across every AI tool you connect.
Your AI's memory for what you actually know: recall across your documents, notes, and meetings
Personal wiki and memory layer for AI assistants. Persistent, structured memory across sessions.
Memory for deep conversational context across any platform
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA persistent memory layer for AI tools that decouples personal data from AI's unstable memory, enabling you to mention information once and have it remembered forever across all conversations.3MIT
- AlicenseNot gradedqualityDmaintenanceProvides a persistent, vendor-neutral memory layer that allows AI tools and agents to share context and knowledge across different platforms while maintaining local data ownership. It enables users to store, recall, and manage structured memories through hybrid semantic search and automated context assembly.16Apache 2.0
sovseal MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceProvides zero-knowledge, local-first persistent memory for AI assistants with on-device embeddings, cross-platform capture, and zero-RTT semantic recall.7Apache 2.0
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4.2/5.0
Disambiguation5/5
Each tool has a clearly distinct purpose: create, delete, get, save, search, and update operations for tasks, goals, memories, and notes, plus get_user_profile for context loading. There is no overlap in functionality; for example, delete_goal and update_goal serve different lifecycle stages, and search_tasks vs. get_note target different resources. The descriptions reinforce these distinctions, making misselection unlikely.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern, such as create_task, delete_goal, get_note, save_memory, search_tasks, and update_note. There are no deviations in style (e.g., no camelCase or mixed conventions), and the verbs are predictable (create, delete, get, save, search, update). This uniformity enhances readability and predictability for agents.
Tool Count5/5
With 18 tools, the server is well-scoped for its purpose of managing tasks, goals, memories, and notes. Each tool earns its place by covering essential CRUD operations and context loading (e.g., get_user_profile). The count is appropriate, neither too thin nor overwhelming, allowing comprehensive coverage without redundancy.
Completeness5/5
The tool set provides complete CRUD/lifecycle coverage for tasks, goals, memories, and notes, with no obvious gaps. For each resource type, there are create, delete, get, search, and update tools, plus specialized operations like get_user_profile for context and detailed recurrence handling for tasks. The domain is fully covered, enabling agents to perform all necessary operations without dead ends.