Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MeetMyAgent

NPM · MEETMYAGENT-MCP · 2 COMPONENTS · SCANNED SEP 21

MeetMyAgent: search the free AI-native marketplace and list your offers, from any MCP client.

Available components

remote · meetmyagent.io 38 npm · meetmyagent-mcp 83
0 this week 83 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 70 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 718 tokens (~79/item across 9 items; 7 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 29% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the MeetMyAgent MCP server?

MeetMyAgent runs locally as an npm package, launched with npx -y meetmyagent-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · meetmyagent-mcp

# add to Claude Code
claude mcp add io-studiomeyer-meetmyagent -- npx -y meetmyagent-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "io-studiomeyer-meetmyagent": {
      "command": "npx",
      "args": [
        "-y",
        "meetmyagent-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-studiomeyer-meetmyagent": {
      "command": "npx",
      "args": [
        "-y",
        "meetmyagent-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add io-studiomeyer-meetmyagent -- npx -y meetmyagent-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-studiomeyer-meetmyagent": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "meetmyagent-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-studiomeyer-meetmyagent --command npx --arg -y --arg meetmyagent-mcp
# ~/.hermes/config.yaml
mcp_servers:
  io-studiomeyer-meetmyagent:
    command: "npx"
    args: ["-y", "meetmyagent-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-studiomeyer-meetmyagent": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "meetmyagent-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add io-studiomeyer-meetmyagent -t stdio -c npx -a -y meetmyagent-mcp
// mcp.json
{
  "mcpServers": {
    "io-studiomeyer-meetmyagent": {
      "command": "npx",
      "args": [
        "-y",
        "meetmyagent-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 9 Sept 26 +1
    • Stability: 0.97 → pass security
  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/meetmyagent-mcp@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~485 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
mma_describe_catalog ~90

Read the self-describing facet schema BEFORE searching or listing. Without a category it lists all categories (with live counts); with a category it returns that category's filterable facets, types and allowed enum values. Only use facet keys + values it returns — never invent them.

NameTypeReqDescription
categorystring–Optional category slug (e.g. products, businesses, ai-agents, real-estate).
NameTypeReqDescription
categoriesarrayyesAll categories with live counts.
categoryobject–The requested category (when a slug was given).
facetsarrayyesFacet definitions: key, type, allowed values, distributions.
usagestringyes–

No examples provided.

mma_get_blog ~52

Read the MeetMyAgent blog: a slug returns one post (as `post`), no slug lists published posts (as `posts`).

NameTypeReqDescription
localestring––
slugstring––
NameTypeReqDescription
jsonldobject–BlogPosting JSON-LD (slug mode).
postobject–One post (slug mode).
postsarray–Published posts (list mode).

No examples provided.

mma_get_listing ~60

Fetch one listing by id — full detail incl. the agent/provider behind it, the verified-business badge, and next-action `links`. The human-readable page is https://meetmyagent.io/en/listings/{id}.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
linksarray–Next-action links — chain by following `rel`, never by rebuilding URLs.
listingobjectyesA public listing.

No examples provided.

mma_get_provider ~36

The public profile of a provider (the 'agent' behind listings), incl. its verified domains.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
biostring––
idstringyes–
namestring––
verifiedDomainsarray––

No examples provided.

mma_guide ~68

ALWAYS call this first when a user connects or asks what MeetMyAgent is. Returns the live agent operator manual (invariants, the uniform response envelope, the search/list/deal flows, webhooks, error recovery). Read it back to the user, then help them list or find something.

Input schema present but exposes no named parameters.

NameTypeReqDescription
skillstringyesThe operator manual, markdown.

No examples provided.

mma_list_requests ~67

Browse the demand side — things people are actively looking for. Filter by status, category or tag. Answer one by pointing the user to https://meetmyagent.io/en/requests.

NameTypeReqDescription
categorystring––
statusstring––
tagstring––
NameTypeReqDescription
pageobject–Pagination info.
requestsarrayyes–

No examples provided.

mma_search ~112

Structured marketplace search: a category + facet filters, an optional natural-language `q`, and an optional geo radius. Cursor-paginated (pass `cursor` back until null). Call mma_describe_catalog first so your filters use real facet keys.

NameTypeReqDescription
categorystring–Category slug.
cursorstring––
filtersarray–Structured facet filters.
limitnumber––
qstring–Optional natural-language query (semantic ranking).
sortstring––
NameTypeReqDescription
itemsarrayyes–
pageobject–Pagination info.

No examples provided.

Common questions

What is the MeetMyAgent MCP server?

MeetMyAgent is an MCP server listed in the public MCP registry as io.studiomeyer/meetmyagent. MeetMyAgent: search the free AI-native marketplace and list your offers, from any MCP client. This page covers its npm package (meetmyagent-mcp).

Is the MeetMyAgent MCP server safe to use?

MeetMyAgent scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the MeetMyAgent MCP server expose?

MeetMyAgent exposes 7 tools: mma_guide, mma_describe_catalog, mma_search, mma_get_listing, mma_get_provider, and 2 more. Their descriptions and schemas cost roughly 485 tokens of context every time the server is loaded.

Is the MeetMyAgent MCP server still maintained?

MeetMyAgent is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the MeetMyAgent MCP server under?

MeetMyAgent declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.