Vendor: usecentralize.com · entry id 05-centralize · source 05-signals-intent-abm.md line 587
The check could not settle it either way. Unknown is a legal answer and it is published rather than guessed. The status was established on 2026-09-02.
mcp_status, verbatim from the file:
unknown
mcp_url, verbatim from the file:
none locatable. The vendor's own pricing page lists "MCP access" as a named feature of the Pro tier ($49/user/month), which is a first-party claim that an MCP exists: https://www.usecentralize.com/pricing. But no server endpoint, docs page, or setup instructions could be found this pass. usecentralize.com/mcp and usecentralize.com/docs both return HTTP 404, the homepage does not mention MCP, and PulseMCP, Glama, Smithery, mcp.so and GitHub searches returned nothing. Per SCHEMA law 1 an MCP claim requires a URL, so this is recorded as unknown with the pricing page as the evidence of the claim, not as official.
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 centralize-modulesquoted from https://www.npmjs.com/package/centralize-modules on 2026-09-27, via npm, a third party source
Packages seen, with the version on 2026-09-27:
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:
free (for the base product). Free tier is $0/month with 5 standard accounts, automatic org charts and account maps, LinkedIn warm-connection sync, Chrome extension, and email and calendar integrations, with no credit card required and every new signup getting 30 days of Pro. Pro is $49/user/month and is the tier that carries MCP access, Centra, AI priorities and drafted outreach, 50 standard plus 5 smart accounts, and 1,000 email plus 100 phone enrichment credits. Enterprise is custom and adds the Salesforce integration, call-recorder and sequencer integrations, SSO and MFA. NOTE: no REST API is mentioned on any tier.
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 usecentralize.com 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: Open-Wine-Components, bedrocklinux, whitebit-exchange, MythicAgents, Bedrock-OSS. A name match alone is never accepted; the account has to point at the vendor domain.
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.
4 source URLs. Raw sources field, verbatim:
https://www.usecentralize.com/, https://www.usecentralize.com/pricing, https://www.businesswire.com/news/home/20260729724558/en/Centralize-Raises-19M-Led-by-NEA-to-Bring-Relationship-Intelligence-to-the-Core-of-Enterprise-Sales, https://www.ycombinator.com/launches/LUE-centralize-ai-powered-org-charts-for-enterprise-sales
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.