Try Centric relationship intelligence: Brief Me, Relational IP radar, Draft As. Demo data.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://centric-demo-mcp-808053805730.us-central1.run.app/mcp6 tools · 195mslist_demo_contactsList the demo book of business — the fictional contacts Centric is tracking for demo RM Marcus Johnson. Returns name, title, company, R/Y/G health, and days since last touch. Start here.List the demo book of business — the fictional contacts Centric is tracking for demo RM Marcus Johnson. Returns name, title, company, R/Y/G health, and days since last touch. Start here.
No input schema was published for this tool.
get_contact_profileGet the full RM-facing profile for one demo contact: the five Relational IP dimensions as Red/Yellow/Green, a Brief Me summary, cadence note, and current context. No numeric score — RMs see status, not the number.Get the full RM-facing profile for one demo contact: the five Relational IP dimensions as Red/Yellow/Green, a Brief Me summary, cadence note, and current context. No numeric score — RMs see status, not the number.
| Parameter | Type | Description |
|---|---|---|
| contact* | string | Contact id or name, e.g. 'Isabella Chen' |
brief_meThe 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.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.
| Parameter | Type | Description |
|---|---|---|
| contact* | string | Contact id or name, e.g. 'Isabella Chen' |
draft_asDraft 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.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.
| Parameter | Type | Description |
|---|---|---|
| contact* | string | Contact id or name, e.g. 'Isabella Chen' |
| format | string | Draft format. Defaults to email. |
get_radarGet the Relational IP radar shape for a demo contact: five axes, each a Red/Yellow/Green status plus a normalized 0–1 position for rendering the widget. Intentionally returns no numeric score.Get the Relational IP radar shape for a demo contact: five axes, each a Red/Yellow/Green status plus a normalized 0–1 position for rendering the widget. Intentionally returns no numeric score.
| Parameter | Type | Description |
|---|---|---|
| contact* | string | Contact id or name, e.g. 'Isabella Chen' |
demo_temperature_checkWalk 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.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.
| Parameter | Type | Description |
|---|---|---|
| contact* | string | Contact id or name, e.g. 'Isabella Chen' |
| read | string | Optional: the read to simulate. Omit to just see the prompt. |
6 of 6 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Try Centric relationship intelligence: Brief Me, Relational IP radar, Draft As. Demo data.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.