{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"smithery_blake365-usgs-quakes-mcp","slug":"blake365-usgs-quakes-mcp","name":"usgs-quakes-mcp","type":"mcp","url":"https://github.com/blake365/usgs-quakes-mcp","page_url":"https://unfragile.ai/blake365-usgs-quakes-mcp","categories":["mcp-servers"],"tags":["mcp","model-context-protocol","smithery:blake365/usgs-quakes-mcp"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"smithery_blake365-usgs-quakes-mcp__cap_0","uri":"capability://data.processing.analysis.real.time.earthquake.data.retrieval","name":"real-time earthquake data retrieval","description":"This capability allows users to fetch real-time earthquake data from the USGS API using a structured query format. It employs a model-context-protocol (MCP) architecture to facilitate seamless integration with various data consumers, ensuring that requests are efficiently processed and responses are delivered in a consistent format. The use of MCP enables the server to handle multiple concurrent requests while maintaining low latency.","intents":["How can I get real-time earthquake data for my application?","What API can I use to retrieve the latest seismic activity information?","I need to integrate earthquake data into my dashboard."],"best_for":["developers building applications that require live seismic data"],"limitations":["Dependent on the availability and response times of the USGS API, which may vary."],"requires":["Node.js 14+","Access to the USGS API endpoint"],"input_types":["structured queries"],"output_types":["JSON","structured data"],"categories":["data-processing-analysis","api integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_blake365-usgs-quakes-mcp__cap_1","uri":"capability://data.processing.analysis.earthquake.event.filtering","name":"earthquake event filtering","description":"This capability allows users to filter earthquake events based on specific criteria such as magnitude, location, and time range. It leverages a query parsing mechanism that interprets user-defined parameters and constructs appropriate API requests to the USGS service. This filtering process is designed to minimize data transfer by only retrieving relevant information, thus enhancing performance.","intents":["How can I filter earthquake data by magnitude and location?","I want to see only significant earthquakes in the last week.","What options do I have to customize my earthquake data queries?"],"best_for":["data analysts looking to extract specific earthquake data for reports"],"limitations":["Filtering capabilities are limited to the parameters exposed by the USGS API."],"requires":["Node.js 14+","Access to the USGS API endpoint"],"input_types":["filter criteria in structured format"],"output_types":["JSON","filtered structured data"],"categories":["data-processing-analysis","query optimization"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_blake365-usgs-quakes-mcp__cap_2","uri":"capability://data.processing.analysis.batch.data.retrieval.for.historical.earthquakes","name":"batch data retrieval for historical earthquakes","description":"This capability enables users to retrieve historical earthquake data in bulk, allowing for comprehensive analysis over extended periods. It uses a pagination mechanism to handle large datasets efficiently, ensuring that users can access extensive historical records without overwhelming the server or client. The MCP architecture supports this by managing state across multiple requests seamlessly.","intents":["How can I download historical earthquake data for analysis?","What is the best way to access large datasets of past seismic events?","I need to pull historical earthquake data for a research project."],"best_for":["researchers and data scientists analyzing seismic trends"],"limitations":["Large data requests may lead to slower response times due to pagination."],"requires":["Node.js 14+","Access to the USGS API endpoint"],"input_types":["pagination parameters"],"output_types":["JSON","bulk structured data"],"categories":["data-processing-analysis","bulk data handling"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":25,"verified":false,"data_access_risk":"moderate","permissions":["Node.js 14+","Access to the USGS API endpoint"],"failure_modes":["Dependent on the availability and response times of the USGS API, which may vary.","Filtering capabilities are limited to the parameters exposed by the USGS API.","Large data requests may lead to slower response times due to pagination.","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.16,"ecosystem":0.48999999999999994,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:25.636Z","last_scraped_at":"2026-05-03T15:19:15.092Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=blake365-usgs-quakes-mcp","compare_url":"https://unfragile.ai/compare?artifact=blake365-usgs-quakes-mcp"}},"signature":"/tv/z5Ybk9bclXSpd4eLgppN181QqTRSr06iWd1dNfGc0q6hz490e2916YR7mHLt2qjhbaMgPvbul9/SYqsKBw==","signedAt":"2026-07-08T20:09:07.402Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/blake365-usgs-quakes-mcp","artifact":"https://unfragile.ai/blake365-usgs-quakes-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=blake365-usgs-quakes-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}