Census MCP by usefulapi
REMOTE · CENSUS.USEFULAPI.IO
List reverse-ETL sources, destinations, models, syncs and runs; trigger syncs into SaaS tools.
Available components
Last scanned (44 minutes ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Data and Analytics
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 −63
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “check_connected_warehouse_sources_and_segments” functional
- New prompt “check_recent_sync_runs_and_their_status” functional
- New prompt “read_the_sql_behind_a_model” functional
- New prompt “see_where_each_sync_sends_its_data” functional
- New prompt “start_a_sync_run” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 0
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://census.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of census.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://census.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/census/ |
| http (plaintext) | http://census.usefulapi.io/mcp | Inconclusive | 302 | http://census.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
census_get_destination Get destination ~45
Get a single destination connection by id. Census: GET /destinations/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The resource id (a numeric id, passed as a string). |
No output schema declared.
No examples provided.
census_get_model Get model ~48
Get a single model by id, including its SQL/query. Census: GET /models/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The resource id (a numeric id, passed as a string). |
No output schema declared.
No examples provided.
census_get_source Get source ~44
Get a single source connection by id. Census: GET /sources/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The resource id (a numeric id, passed as a string). |
No output schema declared.
No examples provided.
census_get_sync Get sync ~47
Get a single sync's full configuration by id. Census: GET /syncs/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The resource id (a numeric id, passed as a string). |
No output schema declared.
No examples provided.
census_get_sync_run Get sync run ~52
Get a single sync run by id — status, counts, errors. Census: GET /sync_runs/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The resource id (a numeric id, passed as a string). |
No output schema declared.
No examples provided.
census_list_destinations List destinations ~70
List configured destination connections (SaaS apps data is synced INTO, e.g. Salesforce, HubSpot, Marketo). Census: GET /destinations.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based) for pagination. |
| per_page | integer | – | Number of records per page. |
No output schema declared.
No examples provided.
census_list_models List models ~61
List SQL models / datasets defined in the workspace (the queries that produce rows to sync). Census: GET /models.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based) for pagination. |
| per_page | integer | – | Number of records per page. |
No output schema declared.
No examples provided.
census_list_segments List segments ~51
List audience segments defined in the workspace. Census: GET /segments.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based) for pagination. |
| per_page | integer | – | Number of records per page. |
No output schema declared.
No examples provided.
census_list_sources List sources ~64
List configured data warehouse sources (Snowflake, BigQuery, Redshift, Databricks, etc.). Census: GET /sources.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based) for pagination. |
| per_page | integer | – | Number of records per page. |
No output schema declared.
No examples provided.
census_list_sync_runs List sync runs ~80
List sync run history (each run's status, records processed, timing). Filter by sync_id. Census: GET /sync_runs.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based) for pagination. |
| per_page | integer | – | Number of records per page. |
| sync_id | integer | – | Filter runs to a single sync id. |
No output schema declared.
No examples provided.
census_list_syncs List syncs ~78
List syncs (a sync maps a source model to a destination object and keeps them in sync). Returns id, label, status, source_attributes, destination_attributes. Census: GET /syncs.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (1-based) for pagination. |
| per_page | integer | – | Number of records per page. |
No output schema declared.
No examples provided.
census_list_workspaces List workspaces ~33
List workspaces in the organization (note: usually requires an organization-level token). Census: GET /workspaces.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
census_trigger_sync Trigger sync ~107
TRIGGERS a sync run for the given sync id — this KICKS OFF a live data sync that writes records into the connected destination SaaS tool. Set force_full_sync=true to re-sync all rows instead of just changes. Census: POST /syncs/{id}/trigger.
| Name | Type | Req | Description |
|---|---|---|---|
| force_full_sync | boolean | – | Re-sync ALL rows instead of just changes since the last run. |
| id | string | yes | The resource id (a numeric id, passed as a string). |
No output schema declared.
No examples provided.
How do I install the Census MCP by usefulapi server?
Census MCP by usefulapi is a hosted endpoint at https://census.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · census.usefulapi.io
claude mcp add --transport http io-usefulapi-census 'https://census.usefulapi.io/mcp'
What is the Census MCP by usefulapi server?
Census MCP by usefulapi is listed in the public MCP registry as io.usefulapi/census. List reverse-ETL sources, destinations, models, syncs and runs; trigger syncs into SaaS tools. This page covers its hosted endpoint (https://census.usefulapi.io/mcp).
Is the Census MCP by usefulapi server safe to use?
Census MCP by usefulapi scores 18 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Census MCP by usefulapi server expose?
Census MCP by usefulapi exposes 13 tools: census_list_sources, census_get_source, census_list_destinations, census_get_destination, census_list_models, and 8 more. Their descriptions and schemas cost roughly 780 tokens of context every time the server is loaded.
Does the Census MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Census MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Census MCP by usefulapi server still maintained?
Census MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Census MCP by usefulapi server?
VerifyMCP ran 4 checks on Census MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Census MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.