Home / MCP registry index / io.github.helpmyagent/helpmyagent

HelpMyAgent

io.github.helpmyagent/helpmyagent in the official MCP registry. Endpoint https://api.helpmyagent.com/mcp.

The registry describes it as: Pay-per-call data APIs for AI agents: business, compliance, procurement, VAT and IBAN via x402.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http helpmyagent https://api.helpmyagent.com/mcp

{
  "mcpServers": {
    "helpmyagent": {
      "url": "https://api.helpmyagent.com/mcp"
    }
  }
}

code --add-mcp '{"name":"helpmyagent","type":"http","url":"https://api.helpmyagent.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

search_apis describe_api list_categories company_fr_aids company_fr_benchmark company_fr_certifications company_fr_changes company_fr_closures company_fr_compare company_fr_compliance company_fr_default_score company_fr_director_mandates company_fr_directors company_fr_e_invoice company_fr_establishments company_fr_events company_fr_financials company_fr_history company_fr_industrial_risk company_fr_intelligence company_fr_invoice_check company_fr_kyb_batch company_fr_legal_announcements_search company_fr_lobbying company_fr_nearby company_fr_new company_fr_opportunities company_fr_payment_context company_fr_peers company_fr_profile company_fr_prospecting company_fr_public_contract_competitors company_fr_public_contracts company_fr_public_contracts_eu company_fr_regulatory_approvals company_fr_report company_fr_risk company_fr_risk_reading company_fr_search company_fr_sector_statistics company_fr_signals company_fr_successions company_fr_supplier_verification company_fr_verify compliance_name_screen iban_validate procurement_fr_awards procurement_fr_buyer_profile procurement_fr_deadlines procurement_fr_market procurement_fr_search procurement_fr_trends real_estate_fr_dpe real_estate_fr_market real_estate_fr_parcel real_estate_fr_risks real_estate_fr_transactions real_estate_fr_valuation vat_eu_validate

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-helpmyagent-helpmyagent/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-helpmyagent-helpmyagent)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers