Atlas entry

`opexvo.com`

7 capabilities over MCP 2025-11-25. First atlas observation.

Observed 12 Nov 2026, 18:18 UTC · passive: no tools called, no credentials sent

Capability facts

As observed from outside, at the time below

Observed: 12 Nov 2026, 18:18 UTC
Signed: 12 Nov 2026, 19:08 UTC

Protocols: MCP
Tools: 7
Declared sign-in: None declared

Effects counted AI readings, beta

Moves money: 0
Deletes or cancels records: 0
Sends messages to people: 0
Changes permissions: 0
Runs code: 0
Asks a person: 0

7 tools examined; 7 counted above a measured threshold.

Declared vs read disagreements

Declared read-only, read as writing: 0
Declared destructive, read as not writing: 0
Declared non-destructive, read as deleting: 0
Declared closed-world, read as reaching out: 0

Change since previous: First observation
Label status: Current

Atlas history

1 observation

12 Nov 2026, 18:18 UTC7 capabilities · MCP 2025-11-25 · MCP endpoint truncated · 1 incomplete inventory groupFirst observation
Fingerprint and versions
Fingerprint
c2fc4e37ce8bb5c3ac696b94c1b55c5d76d6c28ad499855556cc0b5df19425ab (incomplete)
Passport schema
0.5.0, passport-semantic-v4
Consistency
MCP_PROMPTS_ADVERTISEMENT_LIST: not applicable · MCP_RESOURCES_ADVERTISEMENT_LIST: indeterminate · MCP_TOOLS_ADVERTISEMENT_LIST: match · OPENAPI_MCP_EXPLICIT_MAPPING: not applicable

Each class compares an observation with the previous atlas observation. Runs of unchanged observations are grouped. Struck values are what the previous observation recorded; inserted values are what this one recorded.

Declared and observed

Tool declarations are unavailable for this entry.

A disagreement is not a finding about the service: either side can be wrong. How we compare declarations and readings.

About this entry

com.opexvo/site
Listed
Official MCP Registry · first listed 3 Nov 2026 · last listed 3 Nov 2026

Passive observations of a public interface listed in the Official MCP Registry. An observation does not verify security, ownership or compliance, and InterfaceDelta assigns no scores or rankings. Methodology · Report an inaccuracy · Ask for removal

Identity and snapshot

Target key: sha256:fbc58877bb7ff50f44062fa3d1f2d1c67fbb6327809f67d28331be2524205264
Locator SHA-256: ac357549fdfc96799bf38ce41dffcdd593319aa4351317b95860c35fc0aa386a
Snapshot generated: 13 Nov 2026, 01:06 UTC

The entry is one exact observed target, not a real-world service identity, and implies no ownership. Endpoint paths are not published; the locator hash lets an operator confirm their own URL.