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.

CRM

REMOTE · API.MCP.AI

Your own CRM, fully customizable and agent-driven. Start with contacts, companies and a sales pipeli

Available components

0 this week 77 Trust /100

Last scanned (12 hours ago)

Scores higher than 69% of remote servers

Reachable. Last reached 5 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 3395 tokens (~94/item across 36 items; 36 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 37 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
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.

  • 5 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.407 → 0.9.408 functional
  • 4 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.406 → 0.9.407 functional
  • 3 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.398 → 0.9.406 functional
  • 31 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.397 → 0.9.398 functional
  • 28 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.394 → 0.9.397 functional
  • 27 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.388 → 0.9.394 functional
  • 25 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.387 → 0.9.388 functional
  • 24 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Server version: 0.9.381 → 0.9.387 functional
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 5 Nov 2026 · Probed https://api.mcp.ai/p_crm

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.ai CN=WE1,O=Google Trust Services,C=US 28 Sept 2026 27 Dec 2026 ECDSA 256 ECDSA-SHA256 1bf4d405299e078a0e62ff16cded599b
SANs: mcp.ai, *.mcp.ai
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.mcp.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
mcp.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.mcp.ai/p_crm Verified 200
http (plaintext) http://api.mcp.ai/p_crm Inconclusive 406
MCP tools · 36 exposed · ~3,271 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
authenticate ~99

MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

NameTypeReqDescription
tokenstring––

No output schema declared.

No examples provided.

connect ~42

Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

crm_add_field ~125

Adiciona um CAMPO custom a um objeto (sem migração; registros antigos ficam sem a key). Tipos: string text integer float boolean date datetime singleselect multiselect email phone url currency relation user_ref json group.

NameTypeReqDescription
accountstring––
indexedboolean––
keystringyes–
labelstring––
objectstringyes–
optionsstring––
relationstring––
requiredboolean––
typestringyes–
uniqueboolean––

No output schema declared.

No examples provided.

crm_confirm_upload ~72

Confirma o upload depois do PUT na upload_url (o storage valida o tamanho real). Marca o arquivo como pronto e contabiliza no uso. Bulk support: accepts file_ids for batched execution.

NameTypeReqDescription
accountstring––
file_idstringyes–
file_idsarray––

No output schema declared.

No examples provided.

crm_create_records ~98

Cria um registro (ou vários) de um objeto. Passe `object` (ex.: 'contact', 'deal') e `data` (objeto JSON com os campos por key). Para vários, use `records` (array JSON de {data}).

NameTypeReqDescription
accountstring––
datastring––
metadatastring––
objectstringyes–
recordsstring––

No output schema declared.

No examples provided.

crm_define_object ~110

Cria um OBJETO custom no CRM (além de contact/company/deal) e ganha CRUD/API automático. Passe `key` (api name, a-z/0-9/_), `label` e opcionalmente `fields` (array JSON de definições de campo).

NameTypeReqDescription
accountstring––
display_fieldstring––
fieldsstring––
keystringyes–
labelstring––
modulestring––

No output schema declared.

No examples provided.

crm_delete_file ~48

Remove um ou mais arquivos (apaga do storage e libera o espaço contabilizado).

NameTypeReqDescription
accountstring––
file_idstring––
idsarray––

No output schema declared.

No examples provided.

crm_delete_object ~59

Remove um objeto CUSTOM (objetos de sistema não podem ser removidos). Se houver registros, passe delete_records:true para apagar tudo junto.

NameTypeReqDescription
accountstring––
delete_recordsboolean––
objectstringyes–

No output schema declared.

No examples provided.

crm_delete_records ~41

Remove um ou mais registros de um objeto por id.

NameTypeReqDescription
accountstring––
idsarrayyes–
objectstringyes–

No output schema declared.

No examples provided.

crm_describe ~77

Descreve o schema do CRM: todos os objetos (contact, company, deal e quaisquer custom) com seus campos (key, tipo, obrigatório, opções, relações) e o kanban. CHAME ISTO PRIMEIRO para saber quais objetos/campos existem antes de criar/ler registros.

NameTypeReqDescription
accountstring––

No output schema declared.

No examples provided.

crm_download_file ~66

Gera uma URL presigned de download (GET) pra um arquivo. A URL expira em alguns minutos. Bulk support: accepts file_ids for batched execution.

NameTypeReqDescription
accountstring––
file_idstringyes–
file_idsarray––

No output schema declared.

No examples provided.

crm_get_file ~62

Metadados de um arquivo (nome, tamanho, content_type, status, anexo). Bulk support: accepts file_ids for batched execution.

NameTypeReqDescription
accountstring––
file_idstringyes–
file_idsarray––

No output schema declared.

No examples provided.

crm_get_object ~60

Detalha UM objeto: seu rótulo, kanban e todos os campos (key, tipo, obrigatório, opções, relação). Versão focada do crm_describe.

NameTypeReqDescription
accountstring––
objectstringyes–

No output schema declared.

No examples provided.

crm_get_records ~41

Busca um ou mais registros de um objeto por id.

NameTypeReqDescription
accountstring––
idsarrayyes–
objectstringyes–

No output schema declared.

No examples provided.

crm_link_record ~112

Liga um registro a outro por um campo de relação (ex.: vincular um contato a uma empresa). Para relação 'many' adiciona ao conjunto; para 'single' define o alvo. Bulk support: accepts ids, target_ids for batched execution.

NameTypeReqDescription
accountstring––
fieldstringyes–
idstringyes–
idsarray––
objectstringyes–
target_idstringyes–
target_idsarray––

No output schema declared.

No examples provided.

crm_list_accounts ~48

Lista os CRMs conectados neste install. Retorna cada um com id, rótulo e is_default (true quando só há um, não precisa passar `account` nas outras tools).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

crm_list_files ~78

Lista os arquivos do CRM (id, nome, tamanho, status). Opcionalmente filtra os anexados a um objeto/registro. Bulk support: accepts record_ids for batched execution.

NameTypeReqDescription
accountstring––
objectstring––
record_idstring––
record_idsarray––

No output schema declared.

No examples provided.

crm_list_objects ~46

Lista os objetos do CRM (key, rótulo, módulo, kanban). Versão enxuta do crm_describe, sem os campos.

NameTypeReqDescription
accountstring––

No output schema declared.

No examples provided.

crm_list_records ~104

Lista registros de um objeto, com filtro/ordenação/paginação. `filter` é um objeto JSON: {campo: valor} ou {campo: {op: valor}} (ops: eq ne gt gte lt lte in nin contains exists).

NameTypeReqDescription
accountstring––
filterstring––
limitnumber––
objectstringyes–
offsetnumber––
sortstring––

No output schema declared.

No examples provided.

crm_move_stage ~86

Move um registro de um objeto kanban (ex.: deal) para outra etapa do funil. Valida a etapa contra as opções do campo de stage. Bulk support: accepts ids for batched execution.

NameTypeReqDescription
accountstring––
idstringyes–
idsarray––
objectstringyes–
stagestringyes–

No output schema declared.

No examples provided.

crm_publish_file ~113

Torna um arquivo PÚBLICO e devolve uma URL estável (`https://api.mcp.ai/f/<token>`) pra embutir num site (ex.: thumbnail). O objeto continua privado no storage, o token é a chave (revogável com crm_unpublish_file). Egress da visualização pública é contabilizado. Bulk support: accepts file_ids for batched execution.

NameTypeReqDescription
accountstring––
file_idstringyes–
file_idsarray––

No output schema declared.

No examples provided.

crm_related_records ~85

Resolve os registros relacionados de um registro: segue os campos de relação e devolve os registros-alvo (todos, ou só de um `field`). Bulk support: accepts ids for batched execution.

NameTypeReqDescription
accountstring––
fieldstring––
idstringyes–
idsarray––
objectstringyes–

No output schema declared.

No examples provided.

crm_remove_field ~61

Remove um campo CUSTOM (soft-delete: some do schema, mas os valores já gravados ficam preservados). Campos de sistema não podem ser removidos.

NameTypeReqDescription
accountstring––
keystringyes–
objectstringyes–

No output schema declared.

No examples provided.

crm_search ~59

Busca textual nos registros (por nome/título/valores). Opcionalmente restrita a um `object`.

NameTypeReqDescription
accountstring––
limitnumber––
objectstring––
qstringyes–

No output schema declared.

No examples provided.

crm_unlink_record ~104

Desfaz uma relação. Para relação 'many' remove o target_id do conjunto; para 'single' limpa o campo (target_id opcional). Bulk support: accepts ids, target_ids for batched execution.

NameTypeReqDescription
accountstring––
fieldstringyes–
idstringyes–
idsarray––
objectstringyes–
target_idstring––
target_idsarray––

No output schema declared.

No examples provided.

crm_unpublish_file ~61

Revoga o link público de um arquivo (o token para de funcionar na hora). Bulk support: accepts file_ids for batched execution.

NameTypeReqDescription
accountstring––
file_idstringyes–
file_idsarray––

No output schema declared.

No examples provided.

crm_update_field ~139

Edita um campo: rótulo, obrigatório, visível, posição, opções, indexação. Mudança de TIPO só é permitida se for um alargamento seguro (ex.: integer→float); mudança com perda é bloqueada (crie um campo novo e migre).

NameTypeReqDescription
accountstring––
indexedboolean––
keystringyes–
labelstring––
objectstringyes–
optionsstring––
positionnumber––
requiredboolean––
typestring––
visibleboolean––

No output schema declared.

No examples provided.

crm_update_object ~89

Edita um objeto: rótulo, campo de exibição, módulo ou config de kanban (a key é imutável). Vale para objetos de sistema e custom.

NameTypeReqDescription
accountstring––
display_fieldstring––
kanbanstring––
labelstring––
modulestring––
objectstringyes–

No output schema declared.

No examples provided.

crm_update_records ~121

Atualiza um registro (merge parcial) por id. Passe `object`, `id` e `data` (só os campos a mudar; null apaga o campo). Para vários, use `updates` (array JSON de {id, data}). Bulk support: accepts ids for batched execution.

NameTypeReqDescription
accountstring––
datastring––
idstring––
idsarray––
metadatastring––
objectstringyes–
updatesstring––

No output schema declared.

No examples provided.

crm_upload_file ~137

Inicia o upload de um arquivo (até 200 MB) e devolve uma URL presigned (`upload_url`) pra fazer o PUT direto no storage, mais o `file_id`. Depois do PUT, chame crm_confirm_upload. Opcional: anexe a um registro com `object`+`record_id`. Bulk support: accepts record_ids for batched execution.

NameTypeReqDescription
accountstring––
content_typestring––
filenamestringyes–
objectstring––
record_idstring––
record_idsarray––
sizenumberyes–

No output schema declared.

No examples provided.

crm_upload_from_url ~133

Sobe um arquivo A PARTIR DE UMA URL (a plataforma baixa e armazena, até 200 MB) — o jeito do AGENTE subir via API sem segurar os bytes. Devolve o arquivo já pronto. Opcional: anexe a um registro com object+record_id. Bulk support: accepts record_ids for batched execution.

NameTypeReqDescription
accountstring––
content_typestring––
filenamestring––
objectstring––
record_idstring––
record_idsarray––
urlstringyes–

No output schema declared.

No examples provided.

crm_usage ~59

Uso de storage deste CRM: bytes do banco + bytes de arquivos, total em GB, nº de arquivos e egress acumulado. É a base do que é cobrado (storage GB-mês + egress).

NameTypeReqDescription
accountstring––

No output schema declared.

No examples provided.

marketplace ~532

The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.

NameTypeReqDescription
actionstring––
argumentsstring––
cancel_commentstring––
cancel_reasonstring––
conversationstring––
immediateboolean––
limitnumber––
mcp_idstring––
messagestring––
prompt_bodystring––
prompt_categorystring––
prompt_descriptionstring––
prompt_slugstring––
prompt_targetsarray––
prompt_titlestring––
prompt_toolstring––
prompt_varsstring––
querystring––
report_contextstring––
request_detailsstring––
request_namestring––
tier_slugstring––
tool_idstring––

No output schema declared.

No examples provided.

report_bug ~50

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

NameTypeReqDescription
contextstring––
conversationstring––
messagestringyes–

No output schema declared.

No examples provided.

show_version ~17

Show the current MCP platform and adapter versions.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

toolkit_info ~37

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the CRM MCP server?

CRM is a hosted endpoint at https://api.mcp.ai/p_crm, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.mcp.ai

# add to Claude Code
claude mcp add --transport http mcp-dir-crm-mcp 'https://api.mcp.ai/p_crm'
Common questions

What is the CRM MCP server?

CRM is an MCP server listed in the public MCP registry as io.github.mcp-dir/crm-mcp. Your own CRM, fully customizable and agent-driven. Start with contacts, companies and a sales pipeli. This page covers its hosted endpoint (https://api.mcp.ai/p_crm).

Is the CRM MCP server safe to use?

CRM scores 77 out of 100 on VerifyMCP. 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 CRM MCP server expose?

CRM exposes 36 tools: crm_describe, crm_list_objects, crm_create_records, crm_list_records, crm_get_records, and 31 more. Their descriptions and schemas cost roughly 3,271 tokens of context every time the server is loaded.

Does the CRM MCP server require authentication?

No. We connected to CRM without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the CRM MCP server still maintained?

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