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

nova-scotia-open-data

https://scotiasignal.ca

Registry code: 725f54d582e3ce99

api record

Query and explore Nova Scotia open datasets via the Socrata SODA API.

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

endpoint
https://scotiasignal.ca/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 nova-scotia-open-data live?
Yes — it answered the hub's last check (checked 32m ago). It answered 100% of checks over the last 30 days.
Is nova-scotia-open-data free to use?
Yes — the hub reached it with no key and no payment.
What tools does nova-scotia-open-data have?
4 tools: search_datasets, get_dataset_metadata, query_dataset, list_categories.
Is nova-scotia-open-data 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
984ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 283 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search nova scotia open datasets
  • get dataset schema
  • run a soql query on a dataset
takes → gives
text, data → data
tools
4 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

_ what it can do 4 tools
1 open 3 never probed 1 of 4 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_categories reads open 3h ago

    Returns all dataset categories and popular tags available on the Nova Scotia Open Data portal. Use this first to discover valid category names before calling search_datasets with a category filter.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • search_datasets reads unknown never probed

    Search the Nova Scotia Open Data catalog (data.novascotia.ca) for datasets by keyword, category, or tag. Returns dataset names, IDs, descriptions, column names, and direct portal links. Use list_categories first to see valid category and tag names. Use the returned dataset ID with query_dataset or get_dataset_metadata for further exploration.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "tag": {
          "type": "string",
          "description": "Filter by an exact tag name from list_categories (e.g. 'population', 'fisheries')"
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum number of results to return (1–50, default 10)"
        },
        "query": {
          "type": "string",
          "description": "Free-text search query (e.g. 'population', 'fisheries', 'road network')"
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Offset for pagination (default 0)"
        },
        "category": {
          "type": "string",
          "description": "Filter by exact category name from list_categories (e.g. 'Health and Wellness', 'Lands, Forests and Wildlife', 'Crime and Justice', 'Population and Demographics')"
        }
      }
    }
    arguments 32 lines
  • get_dataset_metadata reads unknown never probed

    Retrieve full schema and metadata for a Nova Scotia Open Data dataset by its 8-character identifier (e.g. '3nka-59nz'). Returns all column field names, data types, and descriptions — essential before calling query_dataset so you know the exact field names to use in $select and $where clauses.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "dataset_id"
      ],
      "properties": {
        "dataset_id": {
          "type": "string",
          "description": "8-character Socrata dataset identifier (e.g. '3nka-59nz')"
        }
      }
    }
    arguments 13 lines
  • query_dataset reads unknown never probed

    Run a SoQL query against a Nova Scotia Open Data dataset. SoQL is SQL-like. Key clauses (combine with &): $select=col1,col2 — choose columns $where=field='value' — filter rows (use single quotes for strings) $where=field like '%val%' — partial match $order=field DESC — sort $limit=50 — row count (default 25, max 50000) $offset=50 — pagination $group=field — group by (use with aggregate functions) $q=search term — full-text search Aggregates: count(*), sum(col), avg(col), min(col), max(col) Examples: $where=year='2024'&$order=total DESC&$limit=10 $select=department,count(*)&$group=department&$order=count(*) DESC $where=area like '%Halifax%'&$limit=5 Always call get_dataset_metadata first to find exact field names.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "dataset_id"
      ],
      "properties": {
        "soql": {
          "type": "string",
          "description": "SoQL query string. Multiple clauses joined with '&'. String values in $where must use single quotes: field='value'. Do NOT URL-encode — pass the raw string."
        },
        "limit": {
          "type": "integer",
          "default": 25,
          "maximum": 1000,
          "minimum": 1,
          "description": "Max rows to return (1–1000, default 25). Ignored if $limit is in soql."
        },
        "dataset_id": {
          "type": "string",
          "description": "8-character Socrata dataset identifier (e.g. '3nka-59nz')"
        }
      }
    }
    arguments 24 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 725f54d582e3ce99.

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

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.