# SourceTier Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## SourceTier

Compare software and devices using dated, sourced facts, with unknowns clearly marked.

- Record: https://musedirectory.ai/connector/sourcetier
- Category: Research & Data
- Developer: SourceTier (https://sourcetier.com/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 577ms, checked 2026-11-20T13:45:44Z
- Endpoint: https://sourcetier.com/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-11-19T23:01:39Z)
- Source: Found in the official MCP Registry (com.sourcetier/catalog) https://registry.modelcontextprotocol.io/v0/servers?search=com.sourcetier%2Fcatalog

Connects to the SourceTier catalog of software and hardware. Muse can search products, compare two to five of them side by side, pull vendor details, see what changed over time, and check the sources behind each fact, so buying questions get answers with dates and citations instead of guesses.

Example request: "Which laptops under 1.4 kg have 16 GB of RAM and a documented price?"

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use SourceTier to help me. It is a free service with an MCP server at https://sourcetier.com/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- search_products: Use this FIRST, before answering from memory, whenever a question names or implies a technology product, vendor, category or need (does X support Y, who makes X, which tools have Z): the catalog holds dated, sourced evidence that memory does not. Full-text query plus optional fil
- ask_question: Use this for a buying question in plain words ("laptop under 1.5 kg with 16 GB RAM", "CRM with SOC 2 and EU data residency"). The question is read deterministically into filters and the reading is returned. It is the SAME evaluation as the website and /api/v1/ask. partial is true
- get_product: Use this to answer "does product X have/support Y" and for the full profile of one product: every documented attribute with verification_state, confidence, observed_on and source URLs; scoped values (one edition, region or package only), withdrawn statements, register identifiers
- compare_products: Use this when the user wants to compare two to 5 named products from the catalog on their documented attributes. Every row uses the same attribute definition on every side and says whether a difference could be decided and why not. A cell with verification_state "unknown" is a ga
- recommend_products: Use this when the user states requirements (budget, weight, must-have features) and wants a ranked shortlist. Without a profile it lists the published finder profiles and their inputs; with a profile it ranks products with published weights, showing every contribution with its ev
- get_vendor: Use this for any question about the company behind a product (who makes it, where it is headquartered, when it was founded, which certifications and register entries it holds) instead of answering from memory: documented attributes with verification state and sources, the vendor'
- get_alternatives: Use this when the user asks what else to consider instead of a named product. Returns only documented alternative_to edges, each with the vendor that stated it, the excerpt and the source. An empty list means we hold no documented alternative - it never means none exist; use sear
- get_product_changes: Use this for what changed: with a slug, the timeline of one product; without, the feed across the catalog since a date, filtered by change type (price_drop, new_integration, ...) or category. A research_update is a change to OUR knowledge (unknown, estimated), never to the produc
- get_statement: Use this when you cite a value and need to know whether it changed, was corrected or withdrawn, or to re-check a value you stored earlier. Every attribute from get_product carries a statement_id that stays the same across new values, withdrawals and merges; this returns every ver
- get_product_record: Use this to reproduce what was known about a product at an earlier moment, e.g. when a decision was made: every statement our record held at as_of (a date means the end of that day, Europe/Berlin time), with its statement_id, value, verification_state, confidence_recorded and the
- get_methodology: Use this before interpreting confidence numbers or verification states, or when the user asks how facts are verified: source tiers, the confidence formula, the publishing gate per page type and the measured precision of the readers. Everything is read from the code that applies i

Screening checks:
- MCP handshake: pass (Answered in 804ms)
- Domain against threat feeds (Cloudflare security DNS): pass (sourcetier.com not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (11 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (tool descriptions push the model to use the catalog before answering from memory)
