mcp-registry/com.olyport/ejscreen · v1.26.0
As of 2026-10-21 08:24 UTC, the Olyport Ejscreen MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.
Environmental justice screening indicators, pollution burden, and demographic vulnerability
Claude Code
claude mcp add --transport http olyport-ejscreen-mcp-server https://mcp.olyport.com/ejscreen/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"olyport-ejscreen-mcp-server": {
"type": "http",
"url": "https://mcp.olyport.com/ejscreen/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
15 parameter(s) across 5 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.olyport%2Fejscreen/fixes
{
"name": "get_demographic_indicators",
"description": "Get demographic vulnerability indicators by block group.\n\n Returns demographic data including minority percentage, low income\n percentage, linguistic isolation, education levels, and age\n distributions. These are the demographic components used in\n EJScreen's EJ index calculations.\n\n Args:\n state: Two-letter US state abbreviation (e.g. 'WA', 'CA').\n county_fips: Optional county FIPS code (3-digit or 5-digit).\n If omitted, returns state-level resul",
"inputSchema": {
"type": "object",
"title": "get_demographic_indicatorsArguments",
"required": [
"state"
],
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 50
},
"state": {
"type": "string",
"title": "State"
},
"county_fips": {
"type": "string",
"title": "County Fips",
"default": null
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_ej_county_summary",
"description": "Get EJ indicators for census block groups in a county.\n\n Returns EJScreen environmental justice data for block groups within\n the specified county, sorted by highest overall environmental burden.\n Includes environmental indicators, demographic data, and EJ indexes.\n\n Args:\n state: Two-letter US state abbreviation (e.g. 'WA', 'CA').\n county_fips: County FIPS code, either 5-digit full (e.g. '53033')\n or 3-digit county portion (e.g. '033'). If 3 digits,",
"inputSchema": {
"type": "object",
"title": "get_ej_county_summaryArguments",
"required": [
"state",
"county_fips"
],
"properties": {
"limit": {
"type": "integer",
"title": "Limit",
"default": 50
},
"state": {
"type": "string",
"title": "State"
},
"county_fips": {
"type": "string",
"title": "County Fips"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_ej_data_by_location",
"description": "Get EJScreen environmental justice data for a specific location.\n\n Uses the EPA EJScreen REST broker to retrieve EJ screening indicators\n for a point location with a buffer distance. Returns environmental\n indicators, demographic data, and EJ indexes.\n\n Args:\n latitude: Latitude of the location (e.g. 47.61).\n longitude: Longitude of the location (e.g. -122.33).\n distance: Buffer distance in miles around the point (default 1.0).\n ",
"inputSchema": {
"type": "object",
"title": "get_ej_data_by_locationArguments",
"required": [
"latitude",
"longitude"
],
"properties": {
"distance": {
"type": "number",
"title": "Distance",
"default": 1
},
"latitude": {
"type": "number",
"title": "Latitude"
},
"longitude": {
"type": "number",
"title": "Longitude"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.olyport/ejscreen"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.olyport/ejscreen"}) over MCP.
get_environmental_indicators ~254 tokensget_demographic_indicators ~235 tokensget_ej_county_summary ~232 tokensget_ej_data_by_location ~227 tokensget_ej_state_summary ~189 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.olyport%2Fejscreen?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.olyport%2Fejscreen?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.olyport%2Fejscreen.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.olyport%2Fejscreen.svg :target: https://glimind.com/server/mcp-registry%2Fcom.olyport%2Fejscreen?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:cbb6d1d249dae597…, first seen 2026-10-17, included at leaf 15174 of 38,511. Version history · verify what your client received.
Compare: most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 08:24 UTC, the Olyport Ejscreen MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 2 minutes.
Olyport Ejscreen MCP server advertises 5 tools, including get_demographic_indicators, get_ej_county_summary, get_ej_data_by_location, get_ej_state_summary, get_environmental_indicators.
Point your MCP client at this streamable-http endpoint: https://mcp.olyport.com/ejscreen/mcp
Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.