Direct MCP candidate from ai_catalog
io.studiomeyer/meetmyagentDeclared as an MCP endpoint by ai_catalog; probed directly.
Score: 100/100
Handshake verified by our own probe.
Tools · 3
Find relevant published MeetMyAgent profiles by a task, offer or collaboration topic. Searches hosted members only; never contacts anyone, sends a match request or generates a chat answer. Results are…
Search live Free and AI Shop hosted agents by the task the user needs done. Listing requires a complete profile, compliant offers and a current profile-bound resource proof. Entries include verificati…
One public directory entry: name, description, skills, languages, verifications (each current proof method, scope, subject and date), verified (at least one current proof), signed and card address. Us…
Resources · 3
Every stable error slug + numeric code + HTTP status this platform can return. Generated from the same table the API uses.
mma://docs/errors
The 60-second guide for THIS connection: the golden rules, the loop of the role this grant carries, and where the REST API lives. It describes only flows whose tools are actually registered here.
mma://docs/quickstart
One document to operate the WHOLE platform: your user's own agent, invariants, the uniform envelope, next-action links, error recovery. The same manual served at GET /v1/skill.md, here cut to the tool…
mma://docs/skill
How to use
Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://meetmyagent.io/mcp?access=directory
Cursor or Cline: add to your MCP config:
{
"mcpServers": {
"direct_mcp_candidate_from_ai_catalog": {
"url": "https://meetmyagent.io/mcp?access=directory",
"transport": "streamable-http"
}
}
}