Skip to main content
Glama

Provenio — Art Intelligence

by io.github.mildo-ai
OverviewDiscussionsAdmin

Server Details

Art provenance intelligence — 282K-node knowledge graph with cited answers and honest gaps.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
mildo-ai/provenio
GitHub Stars
0
Server Listing
Provenio MCP Server

TDQS

A4.4/5.0

Scored across 27 tools

Disambiguation5/5

Each tool targets a distinct action and resource type: get_* for entity retrieval, search_* for list discovery, query_* for analytical views, lookup_* for external sources, and find_* for specialized discovery. Descriptions explicitly warn against using the wrong tool (e.g., 'Do NOT use when' statements), making selection unambiguous.

Naming Consistency4/5

Overall pattern is verb_noun with semantic verbs (get, search, query, lookup, find) that align with operation types. Minor inconsistencies exist: bare 'search' and 'fetch' wrappers, and 'byok_external_query' uses an acronym and noun-like structure. These are small deviations in an otherwise systematic naming scheme.

Tool Count4/5

At 27 tools, it's slightly above the ideal 3-15 range, but the server's purpose is a comprehensive art-intelligence platform covering provenance, market, exhibitions, external lookups, and analytics. Each tool earns its place, and the count is justifiable given the domain breadth.

Completeness5/5

The tool surface is remarkably complete for a read-only intelligence platform: entity retrieval (artist, artwork, gallery), discovery (search, find), career analysis, provenance, reception, market aggregates, external museum lookups, and custom BYOK endpoints. No obvious dead ends; even sparse data scenarios return actionable guidance.

Tool Schema Changelog

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

  1. 27 tool updates
    • First observedbyok_external_query
    • First observedcompare_career_patterns
    • First observedfetch
    • First observedfind_comparable_artworks
    • First observedfind_emerging_artists_by_pattern
    • First observedfind_galleries_by_artist
    • First observedget_artist
    • First observedget_artwork
    • First observedget_career_trajectory
    • First observedget_exhibition_history
    • First observedget_gallery_artists
    • First observedget_influence_network
    • First observedget_lineage_cluster
    • First observedget_movement_context
    • First observedget_provenance_chain
    • First observedget_reception_arc
    • First observedlookup_europeana
    • First observedlookup_met_museum
    • First observedlookup_wikidata_art
    • First observedquery_market_summary
    • First observedquery_polity_dispersal
    • First observedquery_reception_price_correlation
    • First observedsearch
    • First observedsearch_artists
    • First observedsearch_artworks
    • First observedsearch_auction_history
    • First observedsearch_galleries

Related MCP Connectors

Related MCP Servers

Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources