_ registry / mcp http-sse · checked 1h ago

skala

https://ai.skala.io

Registry code: 266cbbf8ca61401a

api record

Startup legal platform — incorporate globally, manage fundraising, corporate services, and more.

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

endpoint
https://ai.skala.io/mcp
protocol
http-sse ·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 skala live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is skala free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does skala have?
8 tools: submit_support_request, get_available_companies_for_registration, get_useful_resources, get_available_corporate_services, get_available_doc_gens, get_users_companies, get_company_info_by_id, get_users_tasks_and_deadlines.
Is skala 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 99.6%· all time 99.6%

latency
79ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 280 checks · signed record
  • down → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • list company types for incorporation
  • list corporate legal services
  • list legal document templates
  • view company tasks and deadlines
  • contact legal platform support
takes → gives
text → data
tools
7 reads1 sends messages
_ 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 8 tools
4 open3 auth-required 1 never probed 7 of 8 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.

  • get_available_companies_for_registration reads open 5h ago

    Get the list of company types available for registration on the platform.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_useful_resources reads open 5h ago

    Get a list of useful resources: guides, references, and instructional materials for legal topics and Skala platform usage.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_available_corporate_services reads open 14h ago

    Get corporate services available on the platform — including DBA, name changes, filings, compliance, registered agent, and other company-related services. Always check this when the user asks about any service for their company.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_available_doc_gens reads open 14h ago

    Get the list of legal document templates available for generation on the platform (e.g. NDA, employment agreement, stock purchase agreement). For corporate services like 83(b) filing or registered agent, use get_available_corporate_services instead.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_users_companies reads auth-required 5h ago

    Get the user's companies on the platform.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_company_info_by_id reads auth-required 14h ago

    Get information about the user's company by its ID.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company_id"
      ],
      "properties": {
        "company_id": {
          "type": "string",
          "description": "Company ID on the platform."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_users_tasks_and_deadlines reads auth-required 12h ago

    Get the list of user's tasks and deadlines.

    mcp-tool

    {
      "type": "object",
      "required": [
        "company_id",
        "cursor",
        "limit"
      ],
      "properties": {
        "limit": {
          "type": [
            "integer",
            "null"
          ],
          "description": "Maximum number of items to return (default 10, max 50)."
        },
        "cursor": {
          "type": [
            "integer",
            "null"
          ],
          "description": "Pagination cursor — pass the value from the previous response to get the next page. Null or omit for the first page."
        },
        "company_id": {
          "type": [
            "string",
            "null"
          ],
          "description": "Optional company ID to filter tasks by a specific company."
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • submit_support_request sends messages unknown never probed

    Submit a support request to the Skala team on behalf of the user. Call this when the user needs human assistance that AI cannot provide, the question is too complex or high-risk, or the user explicitly asks for human support. IMPORTANT: Always confirm with the user before calling — describe what you will submit and ask for their approval. Before calling, compile the issue from conversation context into the description.

    mcp-tool

    {
      "type": "object",
      "required": [
        "subject",
        "description",
        "email"
      ],
      "properties": {
        "email": {
          "type": [
            "string",
            "null"
          ],
          "description": "User email for receiving the support response. Required for users without a linked Skala account — ask for it before calling. Null for linked users (Skala already has their email)."
        },
        "subject": {
          "type": "string",
          "description": "Short one-line summary of the support issue."
        },
        "description": {
          "type": "string",
          "description": "Detailed description compiled from conversation context: what the user needs, what was tried, relevant entities."
        }
      },
      "additionalProperties": false
    }
    arguments 26 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 266cbbf8ca61401a.

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