Skip to main content
Glama

Oneinfo Storage

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Italian regulated disclosures direct from 1INFO — keyless, same-day-fresh.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.5% over 18 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-oneinfo-storage
GitHub Stars
0
Server Listing
oneinfo-storage

TDQS

A4.1/5.0

Scored across 38 tools

Disambiguation3/5

Several clusters genuinely overlap: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all answer questions, and polymarket_edges / polymarket_arbitrage / polymarket_edge_tracker / polymarket_kalshi_spread / polymarket_fill_risk all scan prediction-market opportunity. The other clusters (entity_profile vs company_facts vs compare_entities vs resolve_entity vs recent_changes) are also distinguishable only after careful reading. The very verbose descriptions do explicitly cross-reference and route between them, which rescues an otherwise ambiguous set.

Naming Consistency4/5

Almost everything is snake_case verb_noun (validate_claim, resolve_entity, compare_entities, resolution_audit), which is readable and predictable. The deviation is namespacing — some tools carry a pack prefix (polymarket_*, oneinfo_*, pipeworx_*, ask_pipeworx_*) while peers in the same domain do not (bet_research, kalshi_weather_edge). Minor rather than chaotic.

Tool Count3/5

38 tools is heavy by any measure and pushes past the comfortable 3-15 band, with whole families that could be collapsed (the four ask/research variants, the five polymarket variants). It is partly justified because this is a meta-gateway in front of thousands of underlying tools, but the entry surface itself is still bulkier than it needs to be.

Completeness4/5

Lifecycle coverage is strong: memory has remember/recall/forget, subscriptions have subscribe/unsubscribe/list_subscriptions/recent_alerts, and research/comparison/verification/audit paths exist for the main domains. Gaps are minor — no subscription update, no bulk memory clear, and a few soft-failing sources (patents, court calendar) are disclosed rather than hidden.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • Changedrelease_calendar_markets2 fields changed
      • addedOutput schema / properties / empty_reason
        Added value: +{
+  "description": "Present ONLY on a zero-release window: \"no_releases_in_window\". The window was queried and nothing is scheduled — this is an answer, not a failure.",
+  "type": "string"
+}
      • addedOutput schema / properties / hint
        Added value: +{
+  "description": "Present ONLY on a zero-release window: what to change (usually a wider `hours`).",
+  "type": "string"
+}
  2. 38 tool updates
    • First observedai_visibility_check
    • First observedask_pipeworx
    • First observedask_pipeworx_beta
    • First observedask_pipeworx_grounded
    • First observedbet_research
    • First observedcompany_facts
    • First observedcompare_entities
    • First observeddeep_research
    • First observeddiscover_tools
    • First observedentity_profile
    • First observedforget
    • First observedgenerate_llms_txt
    • First observedkalshi_weather_edge
    • First observedlist_subscriptions
    • First observedoneinfo_get_disclosure
    • First observedoneinfo_search_disclosures
    • First observedpipeworx_feedback
    • First observedpipeworx_trending
    • First observedpolymarket_arbitrage
    • First observedpolymarket_edge_tracker
    • First observedpolymarket_edges
    • First observedpolymarket_fill_risk
    • First observedpolymarket_kalshi_spread
    • First observedrecall
    • First observedrecent_alerts
    • First observedrecent_changes
    • First observedrelease_calendar_markets
    • First observedremember
    • First observedresolution_audit
    • First observedresolution_diff
    • First observedresolve_entity
    • First observedscan_competitor_ai_presence
    • First observedscan_dependency
    • First observedsearch_within
    • First observedsubscribe
    • First observedsuggest_questions
    • First observedunsubscribe
    • First observedvalidate_claim

Related MCP Connectors

Related MCP Servers

  • emarket-storage

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables searching and retrieving Italian regulated company disclosures from eMarket Storage (Teleborsa), with filters for issuer, category, market, and publication date, including same-day-fresh PDF links.
    19 npm
    MIT

  • cnmv-filings

    pipeworx-io
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables searching Spanish listed-company regulated disclosures and annual financial reports from the official market regulator, including ESEF packages, with same-day freshness and no API key.
    43 npm
    MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources