_ registry / mcp streamable-http · checked 59m ago

advisor-deadlines

https://advisor-deadlines-mcp.agentbets.workers.dev

Registry code: 818038def902fd2a

api record

Q4 IRS deadline checklist for financial advisors. list_deadlines returns the remaining dated deadlines with sources. check_clients says which clients each deadline hits and why, from account types, birth year, extension status and open items. Use client initials or ids, not names: nothing is stored.

endpoint
https://advisor-deadlines-mcp.agentbets.workers.dev/mcp
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 advisor-deadlines live?
Yes — it answered the hub's last check (checked 59m ago). It answered 100% of checks over the last 30 days.
Is advisor-deadlines free to use?
Yes — the hub reached it with no key and no payment.
What tools does advisor-deadlines have?
2 tools: check_clients, list_deadlines.
Is advisor-deadlines 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
100%

90 days 100%· all time 100%

latency
209ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

_ what it can do 2 tools
1 open 1 never probed 1 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.

  • list_deadlines open 59m ago

    List the Q4 IRS deadlines still ahead (Oct 15 SEP contribution on extension and excess IRA contribution fix; Dec 31 RMD, Roth conversion, QCD), each with due date, who it applies to, days left and the IRS source.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "as_of": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Date to check from (YYYY-MM-DD). Defaults to today, US Eastern."
        }
      },
      "additionalProperties": false
    }
    arguments 11 lines
  • check_clients unknown 59m ago

    For each client, return which remaining Q4 deadlines hit them, why (e.g. 'age 74 with a Rollover IRA', 'on extension with a SEP IRA'), and whether an open item already covers it. Use initials or ids, not names; inputs are not stored.

    mcp-tool

    {
      "type": "object",
      "required": [
        "clients"
      ],
      "properties": {
        "as_of": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Date to check from (YYYY-MM-DD). Defaults to today, US Eastern."
        },
        "clients": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "id"
            ],
            "properties": {
              "id": {
                "type": "string",
                "maxLength": 40,
                "description": "Client id or initials, e.g. C-2087 or MB"
              },
              "accounts": {
                "type": "array",
                "items": {
                  "type": "string",
                  "maxLength": 40
                },
                "maxItems": 30,
                "description": "Account types, e.g. Traditional IRA, Rollover IRA, SEP IRA, SIMPLE IRA, Inherited IRA, Roth IRA, Individual, Joint"
              },
              "birth_year": {
                "type": "integer",
                "maximum": 2030,
                "minimum": 1900
              },
              "open_items": {
                "type": "array",
                "items": {
                  "type": "string",
                  "maxLength": 200
                },
                "maxItems": 30,
                "description": "Open to-dos, e.g. 'Confirm RMD plan'"
              },
              "on_extension": {
                "type": "boolean",
                "description": "Filed a 2025 tax extension"
              }
            },
            "additionalProperties": false
          },
          "maxItems": 500
        }
      },
      "additionalProperties": false
    }
    arguments 59 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 818038def902fd2a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/818038def902fd2a/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/818038def902fd2a/badge.svg)](https://brick.blue/agent/818038def902fd2a?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.