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

Scope

https://scope-continuity2.vercel.app

Registry code: 8274bae1a67a7564

api record

Use Scope for the signed-in freelancer's approved scope, rates, deadlines, and change orders. Call get_approved_record before answering questions about included work, rates, or deadlines. Do not invent a discount. Do not promise work that is not in the approved record. If a tool refuses, tell the freelancer and stop. Do not rephrase the request to get around the refusal. file_change_order only records a proposal. approve_change_order is the only way to apply a discount or new work after approval, and only after the freelancer explicitly approves that order. Tools run only when invoked. Treat…

endpoint
https://scope-continuity2.vercel.app/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 Scope live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is Scope free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does Scope have?
9 tools: save_deadline, create_engagement, save_scope_item, get_approved_record, save_rate, approve_scope, file_change_order, approve_change_order, ….
Is Scope 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
333ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 296 checks · signed record
  • unknown → live
_ what it is for
used for
  • read a freelancer's approved scope
  • record a change order
  • set scope rates and deadlines
takes → gives
text → data
tools
2 reads7 changes data
_ 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 9 tools
1 auth-required 8 never probed 1 of 9 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_engagements reads auth-required 12h ago

    List the signed-in freelancer's engagements. Use a returned id with get_approved_record. Do not guess an engagement.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "offset": {
          "type": "integer",
          "default": 0,
          "maximum": 100000,
          "minimum": 0
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • save_deadline changes data unknown never probed

    Set or move the deadline for one scope item. The date is a calendar day in YYYY-MM-DD form.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "engagementId",
        "scopeItemId",
        "dueOn"
      ],
      "properties": {
        "dueOn": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
        },
        "scopeItemId": {
          "$ref": "#/properties/engagementId"
        },
        "engagementId": {
          "type": "string",
          "format": "uuid"
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • create_engagement changes data unknown never probed

    Create a draft engagement. Draft terms are not an approved commitment until approve_scope.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "clientName",
        "title",
        "currency"
      ],
      "properties": {
        "title": {
          "$ref": "#/properties/clientName"
        },
        "summary": {
          "type": "string",
          "maxLength": 4000
        },
        "currency": {
          "type": "string",
          "pattern": "^[A-Z]{3}$"
        },
        "clientName": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
  • save_scope_item changes data unknown never probed

    Add or update a scope item the freelancer has accepted. After approval, a new item is refused until approve_change_order adds that work. Renaming approved work is refused.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "engagementId",
        "title",
        "description"
      ],
      "properties": {
        "title": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1
        },
        "description": {
          "type": "string",
          "maxLength": 12000,
          "minLength": 1
        },
        "scopeItemId": {
          "$ref": "#/properties/engagementId"
        },
        "engagementId": {
          "type": "string",
          "format": "uuid"
        }
      },
      "additionalProperties": false
    }
    arguments 29 lines
  • get_approved_record reads unknown never probed

    Read the approved scope, rates, deadlines, and change orders before answering. Quote only this record. Draft status is not an approved commitment. Proposed change orders do not authorize a discount or extra work.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "engagementId"
      ],
      "properties": {
        "engagementId": {
          "type": "string",
          "format": "uuid"
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • save_rate changes data unknown never probed

    Set a draft rate, or update an approved rate without lowering it or changing its unit. A lower amount is a discount and is refused. A new rate code after approval is refused. Use file_change_order and approve_change_order for those.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "engagementId",
        "code",
        "label",
        "amountMinor",
        "unit"
      ],
      "properties": {
        "code": {
          "type": "string",
          "maxLength": 40,
          "minLength": 1
        },
        "unit": {
          "enum": [
            "hour",
            "day",
            "fixed"
          ],
          "type": "string"
        },
        "label": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1
        },
        "amountMinor": {
          "type": "integer",
          "maximum": 1000000000000,
          "exclusiveMinimum": 0
        },
        "engagementId": {
          "type": "string",
          "format": "uuid"
        }
      },
      "additionalProperties": false
    }
    arguments 41 lines
  • approve_scope changes data unknown never probed

    Mark the current draft as the approved scope. Pass confirmed true only after the freelancer explicitly approves the current items, rates, and deadlines.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "engagementId",
        "confirmed"
      ],
      "properties": {
        "confirmed": {
          "type": "boolean",
          "const": true
        },
        "engagementId": {
          "type": "string",
          "format": "uuid"
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • file_change_order changes data unknown never probed

    Record a proposed change order. This does not change scope, rates, or deadlines. kind add_work requires workTitle and workDescription. kind discount_rate requires rateCode and a lower amountMinor. kind add_rate requires rateCode, rateLabel, amountMinor, and unit. kind move_deadline requires scopeItemId and dueOn.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "engagementId",
        "kind",
        "summary"
      ],
      "properties": {
        "kind": {
          "enum": [
            "add_work",
            "discount_rate",
            "add_rate",
            "move_deadline"
          ],
          "type": "string"
        },
        "unit": {
          "enum": [
            "hour",
            "day",
            "fixed"
          ],
          "type": "string"
        },
        "dueOn": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
        },
        "summary": {
          "type": "string",
          "maxLength": 1000,
          "minLength": 1
        },
        "rateCode": {
          "type": "string",
          "maxLength": 40,
          "minLength": 1
        },
        "rateLabel": {
          "$ref": "#/properties/workTitle"
        },
        "workTitle": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1
        },
        "amountMinor": {
          "type": "integer",
          "maximum": 1000000000000,
          "exclusiveMinimum": 0
        },
        "scopeItemId": {
          "$ref": "#/properties/engagementId"
        },
        "engagementId": {
          "type": "string",
          "format": "uuid"
        },
        "workDescription": {
          "type": "string",
          "maxLength": 12000,
          "minLength": 1
        }
      },
      "additionalProperties": false
    }
    arguments 68 lines
  • approve_change_order changes data unknown never probed

    Apply one proposed change order after the freelancer explicitly approves that order. Pass confirmed true only then. This is the path that may discount a rate or add work. Calling it is not a substitute for the freelancer's approval.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "engagementId",
        "changeOrderId",
        "confirmed"
      ],
      "properties": {
        "confirmed": {
          "type": "boolean",
          "const": true
        },
        "engagementId": {
          "type": "string",
          "format": "uuid"
        },
        "changeOrderId": {
          "$ref": "#/properties/engagementId"
        }
      },
      "additionalProperties": false
    }
    arguments 23 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 8274bae1a67a7564.

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

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.