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.

io.github.khaoss85/agent-crm

REMOTE · ACCORDO.DEV · SCANNED SEP 20

Read-only docs for the Accordo CRM framework: what it proves, and where it stops.

Available components

+3 this week 88 Trust /100
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 Security80
Transport & Reachability100
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 5091 tokens (~35/item across 142 items; 3 tools + 139 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 Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 57% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the io.github.khaoss85/agent-crm MCP server?

io.github.khaoss85/agent-crm is a hosted endpoint at https://accordo.dev/api/mcp, 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 · accordo.dev

# add to Claude Code
claude mcp add --transport http khaoss85-agent-crm 'https://accordo.dev/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "khaoss85-agent-crm": {
      "url": "https://accordo.dev/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "khaoss85-agent-crm": {
      "type": "http",
      "url": "https://accordo.dev/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.khaoss85-agent-crm]
url = "https://accordo.dev/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "khaoss85-agent-crm": {
      "type": "remote",
      "url": "https://accordo.dev/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add khaoss85-agent-crm --url 'https://accordo.dev/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  khaoss85-agent-crm:
    url: "https://accordo.dev/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "khaoss85-agent-crm": {
      "Transport": "http",
      "Url": "https://accordo.dev/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add khaoss85-agent-crm -t streamable-http -u 'https://accordo.dev/api/mcp'
// mcp.json
{
  "mcpServers": {
    "khaoss85-agent-crm": {
      "type": "http",
      "url": "https://accordo.dev/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 18 Sept 26 0
    • Stability: 0.97 → pass security
  • 17 Sept 26 +1
    • New resource “docs/strategy/FACTORY_ACCORDO_INTEGRATION_ROADMAP.md” functional
  • 16 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.

  • 14 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.

  • 11 Sept 26 +1

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

  • 10 Sept 26 0
    • New resource “docs/strategy/AGENTIC_CRM_RESEARCH_2026_09.md” functional
  • 9 Sept 26 +1

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

  • 7 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 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 · Probed https://accordo.dev/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=accordo.dev CN=YR2,O=Let's Encrypt,C=US 8 Aug 2026 6 Nov 2026 RSA 2048 SHA256-RSA 501433e8cf8011a7fc653ad7ed616dcb828
SANs: accordo.dev
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of accordo.dev. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
accordo.dev. 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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'none'; script-src 'self'; connect-src 'self'; media-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; base-uri 'none'; form-action 'none'; frame-ancestors 'none'
x-content-type-options nosniff
referrer-policy no-referrer
permissions-policy accelerometer=(), camera=(), geolocation=(), gyroscope=(), microphone=(), payment=(), usb=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://accordo.dev/api/mcp Verified 200
http (plaintext) http://accordo.dev/api/mcp HTTPS enforced 308 https://accordo.dev/api/mcp
MCP tools · 3 exposed · ~311 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
check_job ~102

Answer "can this framework do X?" against the CRM jobs-to-be-done index. Returns the matching jobs with their status (not supported / partially supported / technically supported / validated end to end), the tests that prove them, and an explicit answer when the truth is that the job is not supported.

NameTypeReqDescription
limitinteger
querystringyesThe job in plain words, or a JTBD id such as JTBD-CO-01.

No output schema declared.

No examples provided.

get_capability ~118

Resolve a capability from the claims ledger by id (C-nn), by standing-limitation id (L-nn), or by topic. Every capability is returned together with the evidence that proves it and the limitation that bounds it — this tool cannot return one without the other.

NameTypeReqDescription
idstringA claim id such as C-01, or a standing limitation id such as L-01.
limitinteger
topicstringFree text, when the id is unknown. Matches claims and limitations.

No output schema declared.

No examples provided.

search_docs ~91

Keyword search across this framework's documentation set (README, AGENTS, ARCHITECTURE, PRODUCT, DECISIONS and everything under docs/). Returns the file path, the nearest heading and an excerpt for each hit. Read-only; it serves documentation, never customer records.

NameTypeReqDescription
limitinteger
querystringyesWords that must all appear on the same line. Case-insensitive.

No output schema declared.

No examples provided.

Common questions

What is the io.github.khaoss85/agent-crm MCP server?

io.github.khaoss85/agent-crm is an MCP server listed in the public MCP registry as io.github.khaoss85/agent-crm. Read-only docs for the Accordo CRM framework: what it proves, and where it stops. This page covers its hosted endpoint (https://accordo.dev/api/mcp).

Is the io.github.khaoss85/agent-crm MCP server safe to use?

io.github.khaoss85/agent-crm scores 88 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 io.github.khaoss85/agent-crm MCP server expose?

io.github.khaoss85/agent-crm exposes 3 tools: search_docs, get_capability, check_job. Their descriptions and schemas cost roughly 311 tokens of context every time the server is loaded.

Does the io.github.khaoss85/agent-crm MCP server require authentication?

No. We connected to io.github.khaoss85/agent-crm without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.khaoss85/agent-crm MCP server still maintained?

io.github.khaoss85/agent-crm 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.