Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ai.primateintelligence/mcp

REMOTE · API.PRIMATEINTELLIGENCE.AI · 2 COMPONENTS

Video scene understanding for AI agents via the Primate Vision API.

0 this week 52 Trust /100

Last scanned (16 hours ago)

Scores higher than 44% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

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 Security94
Transport & Reachability100
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 4 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.

What we tested

Checks we ran (7)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • MCP protocol

Checks we could not complete (4)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 20 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 19 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 18 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 17 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 16 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 15 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 14 Nov 26 0
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostics

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 21 Nov 2026 · Probed https://api.primateintelligence.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.primateintelligence.ai CN=YE1,O=Let's Encrypt,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA384 5574360629d1ef9a774666c36cb1ebc6c9e
SANs: api.primateintelligence.ai
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.primateintelligence.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
primateintelligence.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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 resource_metadata="https://api.primateintelligence.ai/.well-known/oauth-protected-resource"

Bearer resource_metadata="https://api.primateintelligence.ai/.well-known/oauth-protected-resource"
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer
www-authenticate Bearer resource_metadata="https://api.primateintelligence.ai/.well-known/oauth-protected-resource"

Protected resource metadata

Document https://api.primateintelligence.ai/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://api.primateintelligence.ai/mcp
Authorisation server https://api.primateintelligence.ai

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.primateintelligence.ai/mcp Verified 200
http (plaintext) http://api.primateintelligence.ai/mcp HTTPS enforced 301 https://api.primateintelligence.ai/mcp
MCP tools

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 →

No tool schema has been captured from this endpoint yet.

Install

How do I install the ai.primateintelligence/mcp server?

ai.primateintelligence/mcp is a hosted endpoint at https://api.primateintelligence.ai/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.primateintelligence.ai

# add to Claude Code
claude mcp add --transport http ai-primateintelligence-mcp 'https://api.primateintelligence.ai/mcp'
Common questions

What is the ai.primateintelligence/mcp server?

ai.primateintelligence/mcp is listed in the public MCP registry as ai.primateintelligence/mcp. Video scene understanding for AI agents via the Primate Vision API. This page covers its hosted endpoint (https://api.primateintelligence.ai/mcp).

Is the ai.primateintelligence/mcp server safe to use?

ai.primateintelligence/mcp scores 52 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.

Does the ai.primateintelligence/mcp server require authentication?

Yes. ai.primateintelligence/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 ai.primateintelligence/mcp server still maintained?

ai.primateintelligence/mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the ai.primateintelligence/mcp server?

VerifyMCP ran 7 checks on ai.primateintelligence/mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 3 more. 4 items could not be completed, a gap on our side rather than a finding about ai.primateintelligence/mcp: Schema quality, Stability, Tool coverage and Tool safety. 4 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.