bea
Registry code: 3acf1e388318e263
Unemployment rates, labor force, and Consumer Price Index from the Bureau of Labor Statistics
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.olyport.com/bea/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 bea live?
- Yes — it answered the hub's last check (checked 40m ago). It answered 100% of checks over the last 30 days.
- Is bea free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does bea have?
- 5 tools: get_county_gdp, get_county_personal_income, get_county_employment, get_metro_gdp, list_available_tables.
- Is bea 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.
90 days 99.1%· all time 99.1%
last good check
of 5 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- topic
- finance & markets
- used for
- get county gdp
- get county personal income
- get county employment
- get metro area gdp
- takes → gives
- data → data
- tools
- 5 reads
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.
through this hub
successful
what callers paid
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_available_tables reads open 39m ago
List all available Regional dataset table names from the BEA API. Returns table name codes and descriptions for use with other BEA tools. Useful for discovering which datasets are available.
{ "type": "object", "title": "list_available_tablesArguments", "properties": {} }arguments 5 linesget_county_gdp reads unknown 20h ago
Get GDP by county from the BEA Regional accounts (CAGDP1 table). Returns all-industry GDP for a county or state total. When year is omitted, returns the last 5 available years. GeoFips format: 5-digit county FIPS (e.g. '53067' for Thurston County, WA). For state totals use 2-digit state FIPS + '000' (e.g. '53000' for Washington). Args: county_fips: 5-digit county FIPS code (e.g. '53067') or state total (e.g. '53000'). year: Specific year to retrieve. Omit for last 5 years.
{ "type": "object", "title": "get_county_gdpArguments", "required": [ "county_fips" ], "properties": { "year": { "anyOf": [ { "type": "integer" }, { "type": "null" } ], "title": "Year", "default": null }, "county_fips": { "type": "string", "title": "County Fips" } } }arguments 25 linesget_county_personal_income reads unknown 39m ago
Get personal income by county from the BEA Regional accounts (CAINC1 table). Returns total personal income for a county or state total. When year is omitted, returns the last 5 available years. GeoFips format: 5-digit county FIPS (e.g. '53067') or state total (e.g. '53000'). Args: county_fips: 5-digit county FIPS code (e.g. '53067') or state total (e.g. '53000'). year: Specific year to retrieve. Omit for last 5 years.
{ "type": "object", "title": "get_county_personal_incomeArguments", "required": [ "county_fips" ], "properties": { "year": { "anyOf": [ { "type": "integer" }, { "type": "null" } ], "title": "Year", "default": null }, "county_fips": { "type": "string", "title": "County Fips" } } }arguments 25 linesget_county_employment reads unknown 20h ago
Get total full-time and part-time employment by county from BEA (CAEMP25N table). Returns employment counts for a county or state total. When year is omitted, returns the last 5 available years. GeoFips format: 5-digit county FIPS (e.g. '53067') or state total (e.g. '53000'). Args: county_fips: 5-digit county FIPS code (e.g. '53067') or state total (e.g. '53000'). year: Specific year to retrieve. Omit for last 5 years.
{ "type": "object", "title": "get_county_employmentArguments", "required": [ "county_fips" ], "properties": { "year": { "anyOf": [ { "type": "integer" }, { "type": "null" } ], "title": "Year", "default": null }, "county_fips": { "type": "string", "title": "County Fips" } } }arguments 25 linesget_metro_gdp reads unknown 39m ago
Get GDP by metropolitan statistical area from BEA (MAGDP1 table). Returns all-industry GDP for an MSA. When year is omitted, returns the last 5 available years. Args: msa_code: MSA/CBSA code (e.g. '42660' for Seattle-Tacoma-Bellevue). year: Specific year to retrieve. Omit for last 5 years.
{ "type": "object", "title": "get_metro_gdpArguments", "required": [ "msa_code" ], "properties": { "year": { "anyOf": [ { "type": "integer" }, { "type": "null" } ], "title": "Year", "default": null }, "msa_code": { "type": "string", "title": "Msa Code" } } }arguments 25 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id3acf1e388318e263.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/3acf1e388318e263/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/3acf1e388318e263?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.