Atlas entry

diamonds-expert.com

7 capabilities over MCP. First atlas observation.

Observed · passive: no tools called, no credentials sent · sha256:45fe78…c84c

Surfaces

5 protocols checked

ARDNot foundNo document retrieved
A2ANot found0 skills
MCPValid2025-11-25 · 7 tools · resources not advertised · prompts not advertised
OpenAPINot detected0 operations
WebMCPNot detected0 declarative form tools · experimental
Exact states and meaning
  • ARD
    absent

    Exact state: not found · No document retrieved

    The supported discovery location returned no matching document.

    Not found does not prove the service exposes no such interface elsewhere.

    Not observed / not fetched

  • A2A
    absent

    Exact state: not found · 0 skills

    The supported discovery location returned no matching document.

    Not found does not prove the service exposes no such interface elsewhere.

    Not observed / not fetched

  • MCP
    observed

    Exact state: valid · Revision 2025-11-25 · 7 tools · resources not advertised · prompts not advertised

    A usable protocol document was retrieved and validated.

    Directly observed

  • OpenAPI
    absent

    Exact state: not detected · 0 operations

    No endpoint was established from the evidence and scope that InterfaceDelta inspected.

    Not detected does not prove that no endpoint exists.

    Not observed / not fetched

  • WebMCP
    absent

    Exact state: not detected · 0 declarative form tools · experimental

    No named declarative WebMCP form tools were observed in the origin root HTML.

    Script-registered tools and other pages are not observed, so this does not mean the site has no WebMCP tools.

    Not observed / not fetched

Capabilities

7 · inventory complete

The atlas shows each capability by its plain identifier, inputs and declared sign-in. Publisher descriptions, paths, links and source evidence are not published here.

MCP tools 7

  • estimate_rapaport

    inputs carat (required), clarity (required), color (required), origin (required) and 1 more

  • get_expert_profile
  • knowledge_compare

    inputs options (required)

  • knowledge_next_step

    inputs route_id (required), state

  • knowledge_search

    inputs limit, query (required)

  • knowledge_topic

    inputs topic_id (required)

  • prepare_selection_request

    inputs budget, budget_currency, budget_scope, carat (required) and 12 more

Not observed in this Passport: A2A skills, MCP resources, MCP prompts, OpenAPI operations.

Declared and observed

7 tools declare hints; the AI readings agree with all 0 that have a reading.

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

Atlas history

1 observation

  • 7 capabilities · MCP 2025-11-25 · MCP endpoint validFirst observation
    Fingerprint and versions
    Fingerprint
    45fe783c45458c03022f39ba07d4cce18f12294817833c52f652114fc05fc84c
    Passport schema
    0.5.0, passport-semantic-v4
    Consistency
    MCP_PROMPTS_ADVERTISEMENT_LIST: not applicable · MCP_RESOURCES_ADVERTISEMENT_LIST: not applicable · 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.

About this entry

  • com.diamonds-expert/diamond-sourcing
    Listed

    Official MCP Registry · first listed 2 Nov 2026 · last listed 2 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:f8ef99cb1ab633b5c013da5ca304e8985e547b935b14e2b04bd1b590fd8bacb7
Locator SHA-256
3273639704130f97d4204161a02ce6864c1bc617b5b5c599c6b45e17f741bc47
Snapshot generated
4 Nov 2026, 07:02 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.