Endgame

The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-09-07. On 2026-09-04 the recorded URL served a documentation page, not an MCP endpoint. That is where to read about the server, not where to connect to it. An agent needs the second.

mcp_status, verbatim from the file:

official

mcp_url, verbatim from the file:

https://app.endgame.io/api/v1/mcp ; https://docs.endgame.io/features/mcp-server (endpoint https://app.endgame.io/api/v1/mcp)

• https://app.endgame.io/api/v1/mcp
• https://docs.endgame.io/features/mcp-server

A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.

• create_digest
  Set up a new recurring digest
  evidence: in the vendor docs · calling it writes
• delete_digest
  Delete a digest so it stops running
  evidence: in the vendor docs · calling it writes
• download_skill_assets
  Download a skill's supporting files
  evidence: in the vendor docs · calling it reads
• find_graph_person
  Resolve a person mentioned by name, email, or CRM ID
  evidence: in the vendor docs · calling it reads
• get_digest
  Load a single digest in full
  evidence: in the vendor docs · calling it reads
• get_graph_citations
  Open the sources behind a single piece of context-agent output
  evidence: in the vendor docs · calling it reads
• get_graph_entities
  Load the full record for one or more entities by ID
  evidence: in the vendor docs · calling it reads
• get_graph_facts
  List the facts known about a specific entity
  evidence: in the vendor docs · calling it reads
• get_graph_field_catalog
  Get your organization's field catalog
  evidence: in the vendor docs · calling it reads
• get_graph_index
  Get an overview of your organization's context graph
  evidence: in the vendor docs · calling it reads
• get_graph_person
  Load full detail for one or more people
  evidence: in the vendor docs · calling it reads
• get_graph_relationships
  Fetch the relationships of a single entity
  evidence: in the vendor docs · calling it reads
• get_my_graph_profile
  Resolve the current user to their graph profile
  evidence: in the vendor docs · calling it reads
• get_org_rules
  Load your organization's writing, style, policy, and product guidance
  evidence: in the vendor docs · calling it reads
• list_digests
  List your scheduled digests, including any that are paused
  evidence: in the vendor docs · calling it reads
• list_graph_entities
  Browse entities of a single type with property filters and ordering
  evidence: in the vendor docs · calling it reads
• list_graph_relationships
  List or aggregate relationships org-wide
  evidence: in the vendor docs · calling it reads
• list_my_accounts
  List the accounts you own or are assigned to
  evidence: in the vendor docs · calling it reads
• list_skills
  Discover the expert workflows your organization has authored
  evidence: in the vendor docs · calling it reads
• read_skill
  Load the full instructions for a specific skill
  evidence: in the vendor docs · calling it reads
• search_graph_entities
  Search the context graph by display name, graph ID, or source identifier
  evidence: in the vendor docs · calling it reads
• search_graph_facts
  Semantic search across extracted facts from meetings, emails, and documents
  evidence: in the vendor docs · calling it reads
• search_graph_people
  Search people by their relationship to accounts and companies
  evidence: in the vendor docs · calling it reads
• tell_endgame
  Correct or add to the context graph, and send feedback
  evidence: in the vendor docs · calling it writes
• update_digest
  Change an existing digest's configuration
  evidence: in the vendor docs · calling it reads
• verified_sources
  Display a verified-source footer alongside an answer
  evidence: in the vendor docs · calling it reads

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the tools index.

This is a third party's CLI. It was published by somebody other than the vendor, so it is that author's surface for the vendor's API and not the vendor's published surface. The two must not be read as the same thing.

Install, as the source shows it:

npm install -g @endgame-build/khub

quoted from https://www.npmjs.com/package/@endgame-build/khub on 2026-09-27, via npm, a third party source

Packages seen, with the version on 2026-09-27:

• npm: @endgame-build/khub 0.25.0, third party

A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.

api_gate, verbatim from the file:

unknown/mixed. A self-serve "/signup" flow exists alongside "Get a demo" CTAs, and the docs note "rate limits ... may vary depending on your plan" without publishing any plan or pricing details - could not confirm whether MCP/API access is available below a paid or enterprise tier.

949 of 1252 entries carry an unknown gate. Unknown is a legal answer and it ships as unknown rather than as a guess.

No documentation URL recorded.

727 of 1252 entries are in the same position. Blank is legal and it is published as blank.

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

No GitHub organisation could be tied to endgame.io with evidence on 2026-09-08.

Recorded by the harvest: github candidates were seen but none passed the evidence rules.

5 candidate accounts seen and rejected by the evidence rules: endgameinc, endgame-build, singularity, enqy, Endgame-Labs. A name match alone is never accepted; the account has to point at the vendor domain.

• Research an account before a call

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

• https://endgame.io
• https://docs.endgame.io
• https://docs.endgame.io/features/mcp-server
• https://app.endgame.io/api/v1/mcp

4 source URLs. Raw sources field, verbatim:

https://endgame.io, https://docs.endgame.io, https://docs.endgame.io/features/mcp-server, https://app.endgame.io/api/v1/mcp

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.