Skip to main content
Glama

Sigstore Rekor

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Server Details

Sigstore Rekor — the public transparency log for software signatures.

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.1% over 24 days
Last Tested
Transport
Streamable HTTP
URL
Repository
pipeworx-io/mcp-sigstore-rekor
GitHub Stars
0
Server Listing
sigstore-rekor

TDQS

A3.7/5.0

Scored across 40 tools

Disambiguation2/5

The four rekor_* tools are clearly separated by resource and action, but they are drowned out by a large set of unrelated tools with significant overlap. ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical routers, and the six Polymarket tools plus bet_research overlap heavily, making misselection likely.

Naming Consistency3/5

The rekor_ prefix is consistent and most names use snake_case, but the broader set mixes verb phrases (ask_pipeworx, discover_tools, validate_claim), noun phrases (company_facts, entity_profile, bet_research), and inconsistent suffix patterns (ask_pipeworx_beta, polymarket_edges vs. polymarket_edge_tracker). It is readable but does not follow one predictable convention.

Tool Count2/5

40 tools is far too many for a Sigstore Rekor server, especially since only 4 tools actually concern Rekor while the remaining 36 are an unrelated Pipeworx/prediction-market/AI-marketing suite. This crosses the 'too many' threshold and would badly complicate an agent's tool-selection routing.

Completeness2/5

The Rekor subset covers read-only queries well — log info, search by hash/email, and entry retrieval by UUID or index with inclusion proofs — but it lacks entry submission, public-key search, and direct certificate-based search. Overall, the surface is severely incomplete for a 'Sigstore Rekor' server because the vast majority of tools serve unrelated domains.

Tool Schema Changelog

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

  1. 40 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 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 observedrekor_entry
    • First observedrekor_entry_by_index
    • First observedrekor_log_info
    • First observedrekor_search_by_hash
    • 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

  • histor

    alexar76
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables verification of MCP tool definitions against a signed public transparency log, and querying of historical changes and server metadata.
    1
    MIT

  • ArkForge Trust Layer

    ark-forge
    A
    license
    A
    quality
    B
    maintenance
    Third-party certifying proxy — sign any HTTP call (AI agents, webhooks, microservices) with an independent Ed25519 signature, RFC 3161 timestamp, and Sigstore Rekor anchor.
    4
    148 PyPI
    2
    MIT
  • trustscoreagent-mcp by trustscoreagent

    trustscoreagent-mcpofficial

    trustscoreagent
    A
    license
    A
    quality
    B
    maintenance
    A free, open reputation registry for AI microservices: check a service's trust score before calling it and submit a rating afterward. Ratings can be backed by cryptographic receipts signed by the service and are recorded in a verifiable Merkle audit log.
    3
    Apache 2.0

  • verify-mcp

    ScopeBlind
    A
    license
    A
    quality
    C
    maintenance
    MCP server for offline verification of signed artifacts — receipts, manifests, and audit bundles. MIT licensed, works without accounts or API calls. Tools: self_test, verify_receipt, verify_bundle, explain_artifact.
    4
    62 npm
    6
    Apache 2.0
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources