com.getcims/mcp
REMOTE · API.GETCIMS.COM · SCANNED OCT 5
Manage 230M+ influencers, track campaigns, and access real-time CIMS analytics via AI agents
Available components
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 Security86
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the com.getcims/mcp server?
com.getcims/mcp is a hosted endpoint at https://api.getcims.com/functions/v1/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 · api.getcims.com
claude mcp add --transport http com-getcims-mcp 'https://api.getcims.com/functions/v1/mcp'
{
"mcpServers": {
"com-getcims-mcp": {
"url": "https://api.getcims.com/functions/v1/mcp"
}
}
} {
"servers": {
"com-getcims-mcp": {
"type": "http",
"url": "https://api.getcims.com/functions/v1/mcp"
}
}
} [mcp_servers.com-getcims-mcp] url = "https://api.getcims.com/functions/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-getcims-mcp": {
"type": "remote",
"url": "https://api.getcims.com/functions/v1/mcp",
"enabled": true
}
}
} openclaw mcp add com-getcims-mcp --url 'https://api.getcims.com/functions/v1/mcp' --transport streamable-http
mcp_servers:
com-getcims-mcp:
url: "https://api.getcims.com/functions/v1/mcp" {
"McpServers": {
"com-getcims-mcp": {
"Transport": "http",
"Url": "https://api.getcims.com/functions/v1/mcp"
}
}
} assistant mcp add com-getcims-mcp -t streamable-http -u 'https://api.getcims.com/functions/v1/mcp'
{
"mcpServers": {
"com-getcims-mcp": {
"type": "http",
"url": "https://api.getcims.com/functions/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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
- 14 Sept 26 +1
- DNSSEC: fail → pass ▲ security
- 12 Sept 26 −47
- Endpoint reachability: reachable → behind authorisation ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ 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
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 Oct 2026 · Probed https://api.getcims.com/functions/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.getcims.com | CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US | 9 Jul 2026 | 9 Jan 2027 | RSA 2048 | SHA256-RSA | 4b6a080bb52896332c21808a75c793e |
| SANs: api.getcims.com | ||||||
| CN=GeoTrust TLS RSA CA G1,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 2 Nov 2017 | 2 Nov 2027 | RSA 2048 | SHA256-RSA | d07782a133fc6f9a57296e131ffd179 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.getcims.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| getcims.com. | present | 2371 | 13 | Verified |
| api.getcims.com. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="mcp", resource="https://data.getcims.com/functions/v1/mcp", resource_metadata="https://api.getcims.com//functions/v1/mcp/.well-known/oauth-protected-resource"
Bearer realm="mcp", resource="https://data.getcims.com/functions/v1/mcp", resource_metadata="https://api.getcims.com//functions/v1/mcp/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| www-authenticate | Bearer realm="mcp", resource="https://data.getcims.com/functions/v1/mcp", resource_metadata="https://api.getcims.com//functions/v1/mcp/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://api.getcims.com//functions/v1/mcp/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.getcims.com/functions/v1/mcp |
| Authorisation server | https://exaaeogxwdvqlcboxcfs.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.getcims.com/functions/v1/mcp | Auth required | 401 | |
| http (plaintext) | http://api.getcims.com/functions/v1/mcp | Inconclusive | 404 |
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 →
get_creator CIMS - Get creator profile (paid) ~58
Get a creator profile and headline statistics. When shown as a paid stub, calling this tool returns x402 payment requirements for the REST endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| creatorId | number | – | – |
| handle | string | – | – |
| platform | string | – | – |
No output schema declared.
No examples provided.
get_creator_audience CIMS - Get creator audience (paid) ~43
Get creator audience demographics. When shown as a paid stub, calling this tool returns x402 payment requirements for the REST endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| creatorId | number | – | – |
No output schema declared.
No examples provided.
get_creator_cpm CIMS - Get creator CPM and estimated pay (paid) ~46
Get creator CPM and estimated pay data. When shown as a paid stub, calling this tool returns x402 payment requirements for the REST endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| creatorId | number | – | – |
No output schema declared.
No examples provided.
get_creator_posts CIMS - Get creator posts (paid) ~45
List stored social posts for a creator. When shown as a paid stub, calling this tool returns x402 payment requirements for the REST endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| creatorId | number | yes | – |
No output schema declared.
No examples provided.
get_creator_statistic CIMS - Get creator statistics snapshot (paid) ~44
Get a creator statistics snapshot. When shown as a paid stub, calling this tool returns x402 payment requirements for the REST endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| creatorId | number | – | – |
No output schema declared.
No examples provided.
get_creator_statistics CIMS - Get creator statistics history (paid) ~43
Get time-series creator statistics. When shown as a paid stub, calling this tool returns x402 payment requirements for the REST endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| creatorId | number | – | – |
No output schema declared.
No examples provided.
get_creators CIMS - Search creators (paid) ~43
Search the CIMS creator database. When shown as a paid stub, calling this tool returns x402 payment requirements for the REST endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | – |
No output schema declared.
No examples provided.
What is the com.getcims/mcp server?
com.getcims/mcp is listed in the public MCP registry as com.getcims/mcp. Manage 230M+ influencers, track campaigns, and access real-time CIMS analytics via AI agents. This page covers its hosted endpoint (https://api.getcims.com/functions/v1/mcp).
Is the com.getcims/mcp server safe to use?
com.getcims/mcp scores 34 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 com.getcims/mcp server expose?
com.getcims/mcp exposes 7 tools: get_creators, get_creator_posts, get_creator, get_creator_audience, get_creator_statistics, and 2 more. Their descriptions and schemas cost roughly 322 tokens of context every time the server is loaded.
Does the com.getcims/mcp server require authentication?
Yes. com.getcims/mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the com.getcims/mcp server still maintained?
com.getcims/mcp is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.