io.github.centricai/centric-demo
REMOTE · CENTRIC-DEMO-MCP-808053805730.US-CENTRAL1.RUN.APP
Try Centric relationship intelligence: Brief Me, Relational IP radar, Draft As. Demo data.
Available components
Last scanned (6 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 441 tokens (~73/item across 6 items; 6 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 31 Oct 26 −1
- Tool “get_contact_profile” rewrote its description, which is the text the model reads security
- Tool “get_radar” rewrote its description, which is the text the model reads security
- Tool “list_demo_contacts” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://centric-demo-mcp-808053805730.us-central1.run.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.a.run.app | CN=WR2,O=Google Trust Services,C=US | 7 Oct 2026 | 30 Dec 2026 | ECDSA 256 | SHA256-RSA | 53da11951e5eb49012fb872c3cb3e54d |
| SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 93 more | ||||||
| CN=WR2,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a07c4cded100ad9d66a5107b98 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of centric-demo-mcp-808053805730.us-central1.run.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| run.app. | 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://centric-demo-mcp-808053805730.us-central1.run.app/mcp | Verified | 200 | |
| http (plaintext) | http://centric-demo-mcp-808053805730.us-central1.run.app/mcp | HTTPS enforced | 302 | https://centric-demo-mcp-808053805730.us-central1.run.app/mcp |
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 →
brief_me ~71
The Brief Me hero tool. Returns a synthesized pre-interaction brief for a demo contact — personality read, what to open with, what to avoid — plus a cadence heads-up when the relationship is in a Watch state.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | yes | Contact id or name, e.g. 'Isabella Chen' |
No output schema declared.
No examples provided.
demo_temperature_check ~86
Walk through the temperature check interaction for a demo contact: shows the prompt and the Positive / Neutral / Concern options, and returns a canned acknowledgment. Demonstrates the loop without saving anything.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | yes | Contact id or name, e.g. 'Isabella Chen' |
| read | string | – | Optional: the read to simulate. Omit to just see the prompt. |
No output schema declared.
No examples provided.
draft_as ~90
Draft outreach to a demo contact in a chosen format: email, text, linkedin, or talking_points. Demonstrates Centric's Draft As feature — the draft is grounded in the contact's brief context. Demo only; nothing is sent or logged.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | yes | Contact id or name, e.g. 'Isabella Chen' |
| format | string | – | Draft format. Defaults to email. |
No output schema declared.
No examples provided.
get_contact_profile ~77
Get the full profile Marcus sees for one demo contact: the five Relational IP™ dimensions as red, yellow or green, a Brief Me summary, cadence note, and current context. No numeric score: Marcus sees status, not the number.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | yes | Contact id or name, e.g. 'Isabella Chen' |
No output schema declared.
No examples provided.
get_radar ~72
Get the Relational IP™ radar shape for a demo contact: five axes, each a red, yellow or green status plus a normalized 0–1 position for rendering the widget. Intentionally returns no numeric score.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | yes | Contact id or name, e.g. 'Isabella Chen' |
No output schema declared.
No examples provided.
list_demo_contacts ~45
List the fictional contacts Marcus Johnson is tracking in this demo. Returns name, title, company, health as red, yellow or green, and days since last contact. Start here.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.centricai/centric-demo MCP server?
io.github.centricai/centric-demo is a hosted endpoint at https://centric-demo-mcp-808053805730.us-central1.run.app/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 · centric-demo-mcp-808053805730.us-central1.run.app
claude mcp add --transport http centricai-centric-demo 'https://centric-demo-mcp-808053805730.us-central1.run.app/mcp'
What is the io.github.centricai/centric-demo MCP server?
io.github.centricai/centric-demo is an MCP server listed in the public MCP registry as io.github.centricai/centric-demo. Try Centric relationship intelligence: Brief Me, Relational IP radar, Draft As. Demo data. This page covers its hosted endpoint (https://centric-demo-mcp-808053805730.us-central1.run.app/mcp).
Is the io.github.centricai/centric-demo MCP server safe to use?
io.github.centricai/centric-demo scores 79 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.centricai/centric-demo MCP server expose?
io.github.centricai/centric-demo exposes 6 tools: list_demo_contacts, get_contact_profile, brief_me, draft_as, get_radar, demo_temperature_check. Their descriptions and schemas cost roughly 441 tokens of context every time the server is loaded.
Does the io.github.centricai/centric-demo MCP server require authentication?
No. We connected to io.github.centricai/centric-demo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.centricai/centric-demo MCP server still maintained?
io.github.centricai/centric-demo 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.