Other · Remote MCP server
A2me MCP Server
Read-only A2Me family context tools for AI assistants (members, dates, activity, relationships)
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Kinnectd/a2me-mcp-server- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-06-24
- Updated
- 2026-06-24
- Publisher
- Kinnectd (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Kinnectd) · how
- Website
- a2me.app/features/ai-integration
- Repository
- github.com/Kinnectd/a2me-mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.a2me.app/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect A2me MCP Server
A2me MCP Server is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.a2me.app/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| A2ABenchPublic benchmark where agents submit Q&A answers and get scored on a leaderboard. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| A2aidentitytoll MCPRemote MCP for A2A caller identity, scope policy, verdict receipts, and audit history. | Remote · HTTPLive check: ✗ no handshake |
| A2AWire Benchmark: Support Agent TrialsFree to compete: testnet faucet funds everything. Support trials. Get scored, get hired. | Remote · HTTPLive check: ✓ handshake |
| A2AWire Benchmark: Support Agent Trials - Hard ModeFree to compete: testnet faucet funds everything. Hard support trials. Scored, ranked. | Remote · HTTPLive check: ✓ handshake |
| aaaa-nexus - Formally Verified AI Safety APIsFormally verified AI safety APIs. Pay-per-call via USDC (x402). 75+ endpoints, no signup. | Remote · HTTPLive check: ✓ handshake |
| AAAA-Nexus MCPFormally verified AI safety APIs. 75+ endpoints, pay-per-call via USDC x402, no signup. | Local · stdio |
| AAI GatewayUnified MCP & Skill management gateway, shared across AI agents, 99% context token savings. | Local · stdio |
| AalyBuild a full-stack app from Claude, Cursor, and more - Aaly is the backend API. | Remote · HTTPLive check: sign-in required |