ConnectorNo auth
730,642 tools. Updated 2026-10-31 21:28
"DAF" matching MCP tools:
- Check live availability and exact prices at Landhaus Apartments Prägant for concrete dates and a party. Use this whenever a guest names dates — it is the main tool. It applies the booking rules (arrival days, minimum stay, closures), recommends the apartment that suits the party best (with reasons, e.g. 2 separate bedrooms for families) and lists the free apartments with the total split into stay, final cleaning and tourist tax, the payment and cancellation terms, the website offers valid for the stay and a pre-filled booking link per apartment. If the wish is not bookable it returns the nearest bookable alternative dates with prices instead; parties larger than one apartment get a combination of apartments. Ask for dates, number of adults and the ages of all children first — never assume them. Not for: prices of a whole month without dates (get_rates), apartment descriptions (get_apartment_details). To show the result visually, call render_availability_card with the same arguments. Behaviour: read-only, nothing is booked or reserved, no personal data. Live from the property's booking system (typically 1-2 s, identical requests cached 90 s). Invalid input returns isError with the reason. Returns a text summary plus structuredContent (status, apartments with breakdown and booking_url, alternatives, group, terms, offers, inquiry_url).ConnectorNo auth
- Describe one or all apartments: size, bedrooms, maximum guests, description and page link. Use for questions about the apartments themselves ("how big is #16?", "which apartment has 2 bedrooms?", "which apartments fit 5 people?"). It contains no prices or availability — use check_availability for dates and prices, or get_rates for a month overview. Studio #17 is only listed when asked for by number and is marked as bookable on request. Visual version with photos: render_apartment_gallery. Behaviour: read-only; facts as maintained on praegant.net (synced hourly), answers in milliseconds. Returns text plus structuredContent.apartments (nr, name, m2, bedrooms, max_guests, description, url, on_request, images, and where maintained: beds, outdoor, notes, recommended_for). An unknown number returns the list of existing apartment numbers.ConnectorNo auth
- Show the availability result for given dates and party as an interactive card in the chat. Use after check_availability (or instead of it) when the guest wants to SEE the options: photos, total price with an expandable breakdown, a booking button per apartment, tappable alternative dates. Use check_availability alone when only reasoning over the data or when the client cannot display cards. Behaviour and arguments are identical to check_availability (read-only, live, nothing booked); the result additionally contains small photos and the Google rating. Returns the same text and structuredContent.ConnectorNo auth
- Return curated information about Bad Kleinkirchheim and the house for a topic. Use for "what can we do there?" and house questions: house rules and services (self-catering, no breakfast, bread-roll service, no pets, baby cot/high chair on request, chip access), skiing (winter), hiking, biking and lakes (summer), thermal spas and the in-house sauna (wellness), golf incl. the free green fee and tee-time booking, families, workation, arrival. The Kärnten Card (summer only) and the free green fee are explained exactly. Not for prices or availability (check_availability) and not for apartment facts (get_apartment_details). Behaviour: read-only, static curated content from the property (no web search), instant; topics 'house' and 'wellness' also list the property's official house photos (sauna, steam bath, relaxation room …) — to show them, call render_house_photos, never a web image search (other businesses share the 'Prägant' name). Returns text plus structuredContent.topics (topic, lines), photos (kind, url, caption) and contact details.ConnectorNo auth
- Execute a 4-tool native workflow bundle in parallel in a single call ($0.015-$0.03) and return a unified dossier, saving 3 LLM round-trips. WHEN TO USE: Call for comprehensive multi-source due diligence on a token, company domain, repository, or research topic; use execute_marketplace_tool when you only need a single tool. WHEN NOT TO USE: Do not use for single-endpoint queries or free catalog search. PARAMETER INTERACTIONS: Select bundle_id first and provide the matching entity identifier (token/0x address, domain, repo, or URL) in target. Omit agent_id and tx_hash during your 5 free calls. Read-only and idempotent; results are cached for 1 hour (<5ms cache hit). Pricing: the first 5 calls per agent_id are free and failed calls are never charged. After 5 calls, the tool returns a payment-required quote (not a fatal error) with a $2 Stripe top-up link and Base/Solana USDC addresses; complete payment, then retry with your agd_pass_ key in agent_id or pass tx_hash. Example: execute_workflow_bundle(bundle_id='example')ConnectorNo auth
Matching MCP Servers
- AlicenseNot gradedqualityAmaintenanceEnables natural-language interaction with TypeSafe's Jev decision API, supporting mixed question calls, batch evaluation, model listing, and confidence or composite-score gates over stdio.7MIT
- AlicenseAqualityDmaintenanceMCP server that enables AI assistants to search Irish property listings on Daft.ie via the daftlistings library.5MIT
Matching MCP Connectors
Jewish calendar, zmanim, Shabbat times, parsha, Daf Yomi, and Torah texts with commentaries.
Live availability, rates and offers: Das Landhaus Apartments Prägant, Bad Kleinkirchheim, Austria.
- "Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing entities. type="company" pulls LATEST 10-K revenue + operating income + net income + cash + long-term debt from SEC EDGAR/XBRL (off-calendar fiscal years handled correctly — AAPL Sep, NVDA Jan, etc.). type="drug" pulls FAERS adverse-event counts, FDA approval counts, active trial counts. Results sorted by primary metric so "largest" / "most" / "biggest" reads off the top of the response. Returns paired data + pipeworx:// citation URIs per entity. Replaces 8–15 sequential lookups.ConnectorNo auth
- The same 15-minute crypto "up or down" window priced on polymarket.com, Polymarket US and Kalshi, side by side, with whether each pair is actually the same contract. Pass asset (btc | eth | sol | xrp | bnb) and window ("current" default, "next", "previous", or the window START as ISO such as 2026-10-27T14:15:00Z, on a 15-minute boundary). Per venue: question, Up bid / ask / mid / last, spread_pp, quote_state, volume WITH ITS UNIT, open interest, liquidity, settlement source, comparison basis, when it settles. THE VENUES ARE NOT ONE CONTRACT. Kalshi and Polymarket US settle on CF Benchmarks' BRTI (60-second average at the end against the same at the start): the same bet, so a gap between them is a real disagreement. polymarket.com settles on a Chainlink 60-second TWAP, end against start: same comparison shape, different feed, so a gap against either is partly the contract. `pairs[]` gives equivalent ("true"|"false"|"unclear"|"not_comparable") from resolution_diff for every pair, material_differences, mid_diff_pp (a minus b, in percentage points) and read_as in words. Measured over 30 days of settled windows the Chainlink and BRTI feeds settle a window differently about 1.2-1.8% of the time, almost entirely windows that ended near the threshold (see updown_divergence_rate). `net_spread` is computed only for the pair that is equivalent: the gap in mid terms and at top of book (buy Up where cheaper at the ask, Down where Up is dearer at 1 minus the bid) after BOTH venues' taker fees, each fee carrying its verified-as-of date. Top-of-book size is shown where the venue publishes it (Polymarket US); the Kalshi figure is not in its market payload, so read its order book before sizing. A venue with no market for the window is {status:"not_listed", reason}; one that could not be read is {status:"unavailable", refusal} -- never an empty object, and never the same thing. A one-sided book (typical Polymarket US just before a window is decided) has quote_state "bid_only", a null mid, and the last trade stands in labelled price_basis "last". Quotes are read venue by venue (cached up to 60 seconds), so a gap of a couple of points on a moving window is inside the skew. Only the 15m horizon is offered: it is the one where all three list the same up/down question. For the settled history of how often the venues disagreed, call updown_divergence_rate.ConnectorNo auth
- Get the price level of each apartment for a whole month plus that month's booking rules. Use when the guest has no exact dates yet ("what does a week in July cost?", "when is it cheapest?"). For each apartment it returns the lowest total price of a real reference stay in that month (usually 7 nights, incl. final cleaning and tourist tax) and the arrival days / minimum stay / closures of the month. Not for exact prices on specific dates — use check_availability for that. Visual version: render_rates_card with the same arguments. Behaviour: read-only, live from the booking system (about 1-2 s, cached 5 min). Returns text plus structuredContent (apartments, periods, weeks, perks, offers).ConnectorNo auth
- Realizable-vs-theoretical edge check against live CLOB order-book depth — AND Polymarket's own taker fee, which is never zero and is folded in rather than left for you to add (fleet #3446: r/PredictionsMarkets flagged a "clean" fill that quietly omitted it as optimistic in the direction that loses money). REQUIRES one of `market` (single-market mode) or `event` (basket/partition mode). SINGLE-MARKET: pass a market slug/URL + side (buy_yes|sell_yes|buy_no|sell_no, default buy_yes) + size_usd (default 1000 — max spend on buys, target proceeds on sells); walks the ladder and returns top_of_book, vwap_fill_price, slippage_pp, shares_filled, max_fillable_usd, verdict (clean|degraded|cannot_fill), fee_schedule ({category, taker_rate, exponent, maker_rebate_rate, fees_enabled, basis} — read off THIS market, never assumed free), fee_usd/fee_pp at the actual VWAP fill, breakeven_win_rate_taker (the win probability your side needs just to cover price + fee — ~51.8% on a 50c crypto taker fill, not 50%), breakeven_win_rate_maker (no fee charged to makers — any rebate is in fee_schedule.maker_rebate_rate), and all_in_cost_pp = slippage_pp + fee_pp. BASKET: pass an event slug/URL + side (sell_yes = capture overround by selling every leg, buy_yes = capture underround; default auto from partition sum) + size_usd interpreted as settlement notional S (shares per leg; each share pays $1); returns theoretical_sum vs realizable_sum (top-of-book vs VWAP across all legs), capture_ratio and profit_usd — both NET of every leg's own Polymarket taker fee (capture_ratio_gross/profit_usd_gross keep the pre-fee figures; per_leg[].fee_usd itemizes each leg, summed as fees_usd_total), per-leg fill detail, thin_legs[], max_clean_notional_usd, and forced_directional_risk naming the legs most likely to strand you unhedged. USE THIS before acting on any polymarket_arbitrage SELL/BUY-EVERY-LEG signal or any polymarket_edges trade above ~$500 — theoretical overround on thin books is not capturable, and partial basket fills convert an arb into an unhedged directional position (the dominant loss mode in real arb-bot P&L). Adverse selection while working resting orders is still not modeled.ConnectorNo auth
- Activate 30 days of bearer-token access to every Genuine Good Grants API tool, subject to a 1,000-request fair-use limit. The client supplies its own random token; Genuine Good stores only its SHA-256 hash. Paid HTTP endpoint: https://genuinegood.online/v1/grants/pass. Price: $15.00 USDC via x402 on Base.ConnectorNo auth
- Build a direct booking link on praegant.net, optionally pre-filled with dates, party and apartment. Use when the guest has decided and just wants the link, or wants to book without a price check. Bookings are always completed by the guest on praegant.net — this connector never books, reserves or takes payment by design. check_availability already returns a booking link per free apartment, so call this only when no availability result is at hand. Dates are optional (YYYY-MM-DD); without them the link opens the booking page. Behaviour: read-only, no availability check, instant. Returns text plus structuredContent (booking_url, inquiry_url, phone, email).ConnectorNo auth
- Paid data access. Returns no records itself: it builds the HTTPS query URL for your filters and returns the x402 payment terms (USDC on Base; amsterdam-events $0.005, security-advisories $0.003, vulnerability-watch $0.003, eu-tenders $0.01, uk-tenders $0.005, eu-funding $0.005, cert-advisories $0.003, eu-medicines $0.005, sanctions-entities $0.005, product-recalls $0.005, eu-legislation $0.005, drug-shortages $0.005, public-holidays $0.002 per call). Send a GET to http_endpoint with an x402 client (v2 PAYMENT-SIGNATURE or v1 X-PAYMENT header) to receive up to 100 matching records; no account or API key. Filters per dataset: amsterdam-events: from, to, district, q, min_visitors, limit, offset; security-advisories: cve, vendor, product, q, added_since, ransomware, min_epss, limit, offset; vulnerability-watch: cve, vendor, product, q, min_cvss, kev, updated_since, limit, offset; eu-tenders: country, cpv, q, deadline_after, deadline_before, published_since, min_value, nature, limit, offset; uk-tenders: nation, region, cpv, q, buyer, deadline_after, deadline_before, published_since, min_value, category, sme, status, source, limit, offset; eu-funding: q, programme, status, type, deadline_after, deadline_before, min_budget, limit, offset; cert-advisories: cve, vendor, product, q, cert, country, type, updated_since, kev, limit, offset; eu-medicines: q, type, category, substance, atc, area, holder, status, flag, shortage, updated_since, limit, offset; sanctions-entities: q, list, type, programme, country, identifier, updated_since, limit, offset; product-recalls: q, country, authority, source, category, classification, firm, allergen, status, since, limit, offset; eu-legislation: type, author, subject, q, celex, amends, published_since, in_force, limit, offset; drug-shortages: q, substance, country, status, since, source, holder, area, limit, offset; public-holidays: country, region, date_from, date_to, year, type, q, limit, offset. For free records without filters use get_sample.ConnectorNo auth
- Search 490+ indexed MCP and HTTP 402 (x402) tools by capability keyword and return ranked endpoints with pricing, trust scores, and SLA tiers. WHEN TO USE: Call first to discover which native slug or external endpoint matches your task before calling execute_marketplace_tool. WHEN NOT TO USE: Do not use to execute a tool directly (use execute_marketplace_tool or execute_workflow_bundle). PARAMETER INTERACTIONS: Pass capability keywords or a domain in query; omit agent_id and tx_hash (this discovery tool is always free and never consumes a free trial call). Example: search_x402_mcp_marketplace(query='example')ConnectorNo auth
- Execute any of the 16 native AgentDiet B2A tools by slug or proxy an external marketplace tool URL ($0.001-$0.02 per call). WHEN TO USE: Call to run a single tool discovered via search_x402_mcp_marketplace; use execute_workflow_bundle when you want to run a 4-tool composite bundle in parallel. WHEN NOT TO USE: Do not use for catalog search (use search_x402_mcp_marketplace) or wallet checks (use get_agent_wallet_status). PARAMETER INTERACTIONS: Set target_tool to a native slug (e.g. 'distill', 'token-intel', 'sec-intel', 'github-audit') or external https:// URL, and pass its primary input in input_value. Omit agent_id and tx_hash during your 5 free calls. Read-only and idempotent; results are cached for 1 hour (<5ms cache hit). Pricing: the first 5 calls per agent_id are free and failed calls are never charged. After 5 calls, the tool returns a payment-required quote (not a fatal error) with a $2 Stripe top-up link and Base/Solana USDC addresses; complete payment, then retry with your agd_pass_ key in agent_id or pass tx_hash. Example: execute_marketplace_tool(target_tool='example')ConnectorNo auth
- Inspect an agent's account ledger: remaining free trial calls (out of 5), prepaid USD balance, cumulative spend, total API calls, and total LLM tokens saved. WHEN TO USE: Call before a batch of paid tool executions or after completing a Stripe or USDC top-up to confirm your balance. WHEN NOT TO USE: Do not use to process web content, execute marketplace tools, or submit payments; use the other tools on this server for execution. PARAMETER INTERACTIONS: Omit agent_id to inspect the default trial account derived from your client IP, or pass your explicit agent_id or agd_pass_ session key to check a specific funded wallet. Free and read-only: never charges a fee or consumes a free trial call. Example: get_agent_wallet_status(agent_id='example')ConnectorNo auth
- Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 7,157 across 1860 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbatim quote), confidence, source, fetched_at, refusal_reason:null} on success, OR an explicit refusal {answer:null, refusal_reason:"not_in_source"|"no_tool_match"|"tool_error"|"data_truncated"|"llm_error"} when the data doesn't directly answer. An "llm_error" also carries refusal_cause ("wall" = our time budget ended before any model call was made; "route"|"threw"|"unparseable"|"wall_after_failure" = a model call failed); refusal_reason itself is unchanged. Use whenever an answer will be quoted, cited, or acted on, and the agent must not invent facts (financial verdicts, legal claims, medical lookups, public statements). Costs one extra LLM call vs ask_pipeworx — prefer ask_pipeworx for casual lookups.ConnectorNo auth
- Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market: who publishes the settling number (source), the clock time + timezone it is taken at (falling back to the market TITLE when the clause itself says "the time range specified in the title" — e.g. Polymarket's 15-minute Chainlink TWAP family), the precision of the computation (e.g. "1-minute candle close" vs "60-second trailing average" vs "twap_60s_lookback"/"twap_30s_lookback" vs "election outcome"), comparison_basis — what is compared to what (end_average_vs_start_average | close_vs_open; orthogonal to precision, since venues can share this comparison shape while computing each endpoint differently), the evidence standard (official_source | consensus_reporting | any_credible_report | unspecified), and void_handling (cancellation/postponement settlement — reused verbatim from bet_research's cancellation_rule detector, not re-derived). Parses Polymarket's `description` field (fetched via polymarket_market, or via polymarket_us_search for the .us venue) or Kalshi's `rules_primary` + `rules_secondary` fields (fetched via kalshi_market) with regex + a small vocabulary — no LLM pass, so an unusual clause reports confidence:"low" rather than a guess. Pass `market` as a Polymarket slug/URL (either venue) or a Kalshi market ticker (e.g. "KXBTCD-26SEP1317-T66999.99"); a Kalshi EVENT ticker (e.g. "KXBTCD-26SEP1317") also works — it picks one representative market under that event, since the settlement mechanism is normally shared across all strikes/legs in one event. Use this before treating a polymarket_kalshi_spread row as a real arbitrage: two ladders that look alike can settle on different sources (Polymarket.com's Chainlink TWAP stream vs Kalshi/Polymarket US's CF Benchmarks BRTI), at different times, or with a different lookback window — this tool is how you check. Pair with resolution_diff to compare two markets directly. KNOWN GAP: idiosyncratic phrasing that doesn't match the vocabulary returns confidence:"low" and evidence_standard:"unspecified" rather than an LLM-guessed answer.ConnectorNo auth
- REALIZED win rate by shown price and minutes elapsed for short-horizon crypto up/down markets, net of taker fee — read from our own settled-outcomes archive, not from live prices. Answers the one question no venue will: "a side shown at 82 with five minutes left, how often did it ACTUALLY win?" Returns a grid of (price bucket x minute elapsed) -> n, realized_win_rate_pp, mean_shown_price_pp, calibration_gap_pp (realized minus shown — zero means the book is calibrated), breakeven_win_rate_pp (the shown price plus the taker fee that was actually in force for that market), and net_edge_pp (realized minus breakeven, which is what a taker would have kept). WHY AN ARCHIVE EXISTS AT ALL: a settled 15-minute window is exactly what these venues stop serving. Measured 2026-10-22, a polymarket.com window drops out of the default market listing within minutes of closing (its trade tape and resolution stay retrievable by a closed-market lookup, which the collector now uses), and the other venues serve settled windows only briefly or thinly. So this tool reads a local archive collected window-by-window as they settle. THE THREE VENUES ARE NEVER POOLED. all three compare an END 60-second average with a START 60-second average, but on different feeds: polymarket.com on a Chainlink TWAP, polymarket-us and Kalshi on a CF Benchmarks BRTI simple average. The feeds disagree near the threshold (measured 2026-10-24 on btc: polymarket.com and Kalshi settled differently on 1.6% of windows both hold, polymarket-us and Kalshi on none), so venue:"all" returns one grid PER VENUE and `venues_pooled` is always false. EVERY RATE CARRIES ITS 95% INTERVAL, AND EVERY EDGE SAYS WHETHER IT SURVIVES IT. Each cell gives realized_win_rate_ci95_lo/hi_pp (Wilson, so it never reports an impossible win rate above 100), the same interval carried onto net_edge_ci95_lo/hi_pp, and net_edge_distinguishable_from_zero. READ THAT BOOLEAN BEFORE net_edge_pp: at these sample sizes most cells are false, meaning the interval straddles zero and a net_edge_pp of +4pp is NOT evidence of an edge. For scale, at a 90% win rate even n=300 gives a 95% half-width of ~3.4pp while net edges here run +2 to +4pp — so a comfortable-looking sample still cannot call a small edge real. `verdict` says it per cell in plain words, and the first note says how many cells survived. A THIN CELL WITHHOLDS ITS RATE ENTIRELY. Any bucket holding fewer than 30 settled windows reports status "thin" with realized_win_rate_pp and every interval null rather than printing a rate from a sample too small to mean anything — a 2-sample "100% win rate" is the most misleading thing this tool could say. ALWAYS READ `coverage` BEFORE THE GRID: it gives the first and last window held, windows_total vs windows_settled, every UTC day inside the span with no windows at all, and the longest run of consecutive missing windows. A grid over a store with a three-day hole looks entirely normal and is measuring a different population. mean_fill_price_pp and fill_vs_shown_pp are populated for polymarket.com only — it is the one venue of the three that publishes a trade tape for these markets, so it is the only place realized FILL can be compared with the shown price instead of assumed equal to it.ConnectorNo auth
- Use before Sunday lock for a kick-time checklist of outdoor weather games that need a look. Prefer this over get_flags when the user wants that checklist. Optional weekId (YYYY-wNN); omit it for the current week. Returns FLAG and WATCH games whose roof is outdoor, or retractable and confirmed open, sorted by kickoff. Skips DOME, CLEAR, and closed or fixed roofs. Each game includes matchup, call, confidence, kickoff time, a one-sentence why, and the game page URL.ConnectorNo auth
- Settlement date on the Payments Canada holiday calendar, and the accrual fraction under ACT/360, ACT/365F, 30/360, 30E/360 or ACT/ACT-ISDA. Send all seven inputs, including acknowledge no-ruling-v1 and a freshness_tolerance in whole days written P<n>D. It refuses rather than guesses: a missing acknowledgement or tolerance, a tolerance over the ratified ceiling, calendar data older than your tolerance, a trade date outside the calendar's coverage or not a business day, and any missing, unknown or malformed input. Costs $0.01 in USDC on Base per computed answer, under x402; a refusal is not charged. The answer is the JSON envelope of https://foundry.dap.solutions/api/compute-day-count-to-settlement, byte for byte, with the artifact hash that answered. Full rules: https://foundry.dap.solutions/hub.mdConnectorNo auth