_ registry / mcp streamable-http · checked 5h ago

arcflow-destiny-matrix

https://destinymatrixcalc.com

Registry code: da64051782832dc0

api record

Calculate a Destiny Matrix (numerology) reading from one or two dates of birth. Read-only, no auth.

from a public catalogue that lists it, not from the operator

endpoint
https://destinymatrixcalc.com/api/mcp-public
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is arcflow-destiny-matrix live?
Yes — it answered the hub's last check (checked 5h ago). It answered 96% of checks over the last 30 days.
Is arcflow-destiny-matrix free to use?
Yes — the hub reached it with no key and no payment.
What tools does arcflow-destiny-matrix have?
2 tools: calculate_compatibility, calculate_matrix.
Is arcflow-destiny-matrix safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
95.6%

90 days 97.1%· all time 97.1%

latency
430ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 345 checks · signed record
  • down → live
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
_ what it is for
used for
  • calculate a destiny matrix from a birthdate
  • check numerology compatibility of two people
takes → gives
data → data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • calculate_compatibility reads unknown 14h ago

    Calculate relationship compatibility between two people from their dates of birth, using the Destiny Matrix numerology method. Returns a structured reading of the couple: shared core numbers plus text interpretations for relationship dynamics, finances, conflict points, children, and growth areas. Use this when a user asks how compatible two people are, or wants a numerology compatibility reading based on two birth dates.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "birthdate_a",
        "birthdate_b"
      ],
      "properties": {
        "locale": {
          "enum": [
            "ru",
            "en",
            "es"
          ],
          "type": "string",
          "description": "Language for the text interpretations: \"en\" (default), \"ru\", or \"es\"."
        },
        "birthdate_a": {
          "type": "string",
          "description": "First person's date of birth in DD-MM-YYYY format, e.g. \"15-05-1990\"."
        },
        "birthdate_b": {
          "type": "string",
          "description": "Second person's date of birth in DD-MM-YYYY format, e.g. \"20-08-1995\"."
        }
      }
    }
    arguments 27 lines
  • calculate_matrix reads unknown 14h ago

    Calculate a Destiny Matrix (also known as "Matrix of Destiny" or numerology matrix) from a single date of birth. Returns a structured numerology reading: core numbers (1–22) for personality, talents, money, relationships, life purpose, and inherited/karmic patterns, each with a short text interpretation. Use this when a user asks to compute, build, or interpret a destiny matrix, or wants a numerology personality reading based on a birth date.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "birthdate"
      ],
      "properties": {
        "locale": {
          "enum": [
            "ru",
            "en",
            "es"
          ],
          "type": "string",
          "description": "Language for the text interpretations: \"en\" (default), \"ru\", or \"es\"."
        },
        "birthdate": {
          "type": "string",
          "description": "Date of birth in DD-MM-YYYY format (day-month-year), e.g. \"15-05-1990\"."
        }
      }
    }
    arguments 22 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id da64051782832dc0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/da64051782832dc0/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/da64051782832dc0/badge.svg)](https://brick.blue/agent/da64051782832dc0?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.