Skip to main content
Glama
820,845 tools. Updated 2026-11-22 13:05

"Information or resources related to logs" matching MCP tools:

  • Get build and runtime logs for a deployment. If no deployment_id is provided, returns logs for the latest deployment. Use this after calling deploy to monitor build progress and diagnose failures. Logs include: framework detection output, dependency installation, build steps, container startup, and health check results. If a deployment fails, check the logs for error details — common issues include missing dependencies, build errors, or the app not listening on the correct PORT (check the PORT env var — 8080 for auto-detected frameworks, or the EXPOSE value from Dockerfile).
    ConnectorNo auth
  • Return the safely validated redirect chain. Use only for public HTTP(S) resources; it does not execute JavaScript or bypass access controls. Pass url as an absolute public HTTP(S) URL. Keep fresh=false to allow cache reuse; set fresh=true only when a new upstream fetch is required.
    ConnectorNo auth
  • List up to 100 image references without downloading images. Use only for public HTTP(S) resources; it does not execute JavaScript or bypass access controls. Pass url as an absolute public HTTP(S) URL. Keep fresh=false to allow cache reuse; set fresh=true only when a new upstream fetch is required.
    ConnectorNo auth
  • Discover up to five sitemap links declared by the requested page. Use only for public HTTP(S) resources; it does not execute JavaScript or bypass access controls. Pass url as an absolute public HTTP(S) URL. Keep fresh=false to allow cache reuse; set fresh=true only when a new upstream fetch is required.
    ConnectorNo auth
  • Maps only stable Tier1 finding identifiers to approved Tier1 services and public resources. Call after a Tier1 score or email-domain check. Do not submit prose, URLs, customer information, or invented identifiers. This tool performs no arbitrary fetching, makes no contact request, changes nothing, and stores nothing.
    ConnectorNo auth
  • Free. Sends a message to the human operators of this service: a bug report, a problem with these tools or the documentation, or a suggestion. It is read by people, not processed by software, and nothing is returned beyond an acknowledgement. Do NOT use it for status updates, progress notes, task narration, error logs, or as a fallback when another tool is unavailable or a payment cannot be made -- it cannot complete, retry or work around any task. Name is optional (omit for anonymous feedback); message is limited to 1000 characters.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI agents to query OpenRouter model information including prices, ELO rankings, context, and perform comparisons.
    22 npm
    1
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to investigate very large log files with constant-memory streaming, offering format overviews, filtered searches, error clustering, timelines, request tracing, and window comparisons across plain, gzipped, and rotated logs.
    7
    MIT

Matching MCP Connectors

  • Server-log intelligence: which bots and AI crawlers read your site, and what your pages served.

  • Offline log parsing, CI failures, HTTP capture analysis and bounded JSON configuration validation.

  • Fetch one paper: its summary, authors, venue, figures, linked resources, or full text. Accepts a Lacuna artifact ID or paper URL from search_lacuna, or an outside identifier for the same paper: an arXiv ID (2310.06825), a DOI, or an arXiv, DOI or OpenReview URL. Use this when the user names a specific paper or after a search. For an outside identifier that is not in Lacuna's ML/AI corpus, the result is `found: false` with a note saying so. The default view is a summary; ask for the full text only when the summary does not answer the question. include_resources adds linked resources (code repositories, datasets, models, and demos) in context and full views by default. Pass False to omit them; other views ignore this option. Pass a resource entry's id to get_resource for further details. view selects the response shape. `context` requests Lacuna's compact agent-oriented context by default, while the four single-field views (blog/figures/concepts/neighbors) return isolated sub-resources: - "context" (default, recommended): agent-oriented summary with summary_markdown, authors, and a small figure preview. Start here for almost everything. Available versions are included when present; to read another version, use its artifact ID from the returned version list. - "full": raw upstream paper record. Cheaper than context when you only need basic metadata. - "preview": compact card with unique fields `excerpt`, `excerpt_kind`, `bookmarked`. Use for citation-style display. - "blog": just the summary_markdown content, without the rest of the context envelope. - "figures": just the figures list. - "concepts": just the concepts list. - "neighbors": just the related-papers list. - "fulltext": the paper itself, `max_chars` at a time (default 40,000; 1,000 to 100,000, other values are moved into that range) from `offset`; pass the returned `next_offset` to keep reading. `total_chars` is the length of the whole text, and an `offset` past it returns empty text. `format` says what you got: "latex" is the arXiv LaTeX source without its bibliography (citations appear as \cite keys); "pdf_text" is text extracted from the PDF, where equations and tables can be garbled. Lacuna holds text for most arXiv papers and for fewer papers known only by DOI; a paper without text returns `available: false`. figure_limit (context view only) caps the figure preview (server default 3). Pass 0 to suppress figure previews while keeping a `figures_truncated` signal.
    ConnectorNo auth
  • Use this when the user wants weather history, historical weather data, historical weather by date and location, or a daily weather data download. Reads station observations and generates Excel and CSV weather logs with rain days for construction delay and thresholds. US only; up to five sites and 366 days, from 1900 through today UTC. Files expire in about an hour. Do not use for forecasts, current conditions or certified weather reports.
    ConnectorNo auth
  • Delete ONE AI package resource of a video in one language (eBook, mind map or quiz) — cannot be undone: its content, PDF, images and the published file are removed, also for legacy resources. Same as the dashboard's Remove. Refused while it is still generating (checked before deleting; if that check fails nothing is deleted). Other languages and resources stay. To remove a failed generation card use panda_delete_ai_workflow.
    Connector
    Destructive
    No auth
  • The full text of one help article as Markdown, with links to related articles. Pass the id from help_search, or a keyword: an exact title wins, a keyword several articles share returns them to pick from, anything else gets the best search hit.
    ConnectorNo auth
  • Permanently deletes a private network you added with create_private_network, which stops its billing. It is refused for your default network and for any network a machine is still attached to: delete those machines, or the resources running on them, first. Get the id from list_private_networks.
    Connector
    Destructive
    No auth
  • Submit only the feedback the user explicitly asks to send to AiLinkAny. Requires user_confirmed=true, BUG/FEATURE/OTHER, a short message and a fresh opaque 32 lowercase hex feedback_id. Reuse that ID only for the same submission after transport failure. Never automatically upload files, logs, credentials or competitor feedback; suspected secrets are rejected. At most two new submissions per 10 minutes. Account OAuth identity is authoritative and no device/subscription is required.
    ConnectorOAuth
  • [Requires authentication] Call the authenticate tool first to start or confirm 1inch Business login (initialize 200 is still anonymous). If authenticate or this tool returns HTTP 401, complete OAuth, then retry. Look up production API request logs for your 1inch Business organization to troubleshoot integration issues. Results are always scoped to your authenticated organization. Two modes: 1) By request id: pass requestId (the x-request-id header returned on 1inch API responses). Optionally narrow startTime/endTime (defaults: last 24 hours ending now). 2) Logs in a time window: omit requestId and pass both startTime and endTime (RFC3339). Optionally set logLevel ("info", "warn", or "error") to filter by severity; omit to return all levels. Limits: each call covers at most a 24-hour window; how far back you can query depends on your plan's log retention.
    ConnectorNo auth
  • Find logs matching filter criteria within a time range. Use this as your default starting point for log queries. Returns logs sorted by (timestamp, logId) descending (newest first). When investigating an error or a failure, call list_issues first: Fixter has often grouped it already into an issue with its count, first and last seen and a traceId to search from. Returns the log's main fields by default; pass verbose=true to include its attributes (http/url/… flattened in, plus a `resource` object). Long string values are capped (maxStringChars). For raw columns or custom selection use run_sql. For one row with every attribute, use get_log; a cut value's marker carries the "more" call that reads the rest. Defaults: from: 1 hour before to (or before now) when omitted; set it to read further back to: now when omitted limit: 100 (max 1000) service/level: any Common patterns: - Errors in the last hour: level="ERROR", from=<1h ago> - Logs for a trace: traceId="abc123..." - Whole-token search (case-insensitive): messageContains="timeout" - Substring or regex search: not supported here; use run_sql Returns: logs: array of log objects (lean unless verbose=true) nextCursor: opaque token (null on the last page); pass back as cursor to fetch the next page truncationHint: present when the page was cut to fit the response; nextCursor then reads on from the last log shown explorerUrl: shareable Fixter UI link opening this query in the log explorer — when the user asks to see or browse these logs, send them there rather than reproducing the listing; attach it when citing these logs as evidence (covers the service/level/traceId filters and the window; timestamps display in the viewer's browser timezone) queryStats: rowsReturned, elapsedMs
    ConnectorAPI key
  • Get care plan material for a specific NANDA-style nursing diagnosis: its definition, related factors (the "related to" clause), defining characteristics (the "as evidenced by" clause), SMART goals, interventions, and the conditions where it is a priority. Use when a nursing student asks about a diagnosis rather than a disease, for example "risk for infection", "acute pain", "impaired gas exchange", "ineffective coping" or "risk for falls", or asks how to write a three-part diagnosis or an AEB statement. Educational reference, not medical advice.
    ConnectorNo auth
  • Find out whether your transaction will succeed before you pay for it. Simulates on mainnet and returns the decoded error (translated to plain language), logs, compute units consumed, and expected account changes. Use before submitting any unfamiliar or high-value transaction. Never sends — simulation only. $0.01 per call in USDC on Solana. transaction_base64: base64-encoded signed or unsigned Solana transaction
    ConnectorNo auth
  • USE WHEN asked to explain a crypto-agent concept (what x402 is, how agents hold wallets, what ERC-8004 does) and you want a sourced explainer you can cite. Find slugs with onchain_agent_list_wiki_pages. NOT FOR a specific project (use onchain_agent_get_resource instead) or how the Sato Score works (use onchain_agent_get_score_methodology). RETURNS (json): the full wiki page by slug: summary, why it matters, how it works, key components, examples, risks, related resources/pages. A near-miss slug that plainly means a page ("what-are-erc-8004" or the bare "erc-8004" for "what-is-erc-8004") serves that page and says which one in alias_of; when the slug is also a directory listing, also_listing names onchain_agent_get_resource. An unknown slug is a miss (not an error) carrying the nearest real slugs as suggestions; the Sato Score has no wiki page, so "what-is-sato-score" is a miss that points at onchain_agent_get_score_methodology. Read-only. Example: { slug: "what-are-mcps" }
    ConnectorNo auth
  • Search Windows Event Log entries ingested from Netmon agents. Wraps GET /api/eventlog/list (permission: logs); tag-scoped server-side. Severity is the raw Windows EventRecord.Level: 'logalways'=0 (what Security-channel audit events carry), 'critical'=1, 'error'=2, 'warning'=3, 'information'=4, 'verbose'=5 — pass names or ints. Note 0 is NOT Information. Window: `hours` (1-168, default 24) OR `start_time`+`end_time`. `limit` defaults to 50 (max 500). `total` in the response is the full match count — if it exceeds `limit`, narrow the window or add severity/source/message filters rather than bumping limit. Example: eventlog_search({severity: "error", hours: 4})
    ConnectorNo auth
  • Updates family grouping for one saved own patent using public patent information and related own patents already saved in the connected organisation. Useful for an apparent missing relationship, an unfinished family update, or a requested check against newer public information. Imports already attempt family grouping automatically; routine refresh after import is unnecessary. Related publications must be imported separately before they can be included. Repeating import_patent only retrieves its saved outcome. Existing family relationships are retained, so refresh cannot remove incorrect relationships. Patent text, PDFs, images, legal status and own/competitor classification are unchanged. Competitor records are not supported. Returns counts of added and existing relationships, unresolved or ambiguous matches, and failures, with warnings. It does not return a list of family members. A null links result means the update did not finish; repeating the refresh attempts it again. Results do not establish complete family coverage. Where the organisation is charged in credits, a refresh costs a patent search and is refused once credits are spent.
    ConnectorOAuth
  • Search aggregated logs from Cycle containers. First stop for crash loops, application errors, and confirming "out of memory" / "no space left" style failures. Use after diagnose points at a specific container or instance, or directly when the user names one. Scope with environment for environment-wide logs, add container to narrow, add instance to narrow further — the most specific reference wins. Search is optional; without it the newest lines in the range are returned. Use search_type "regexp" with RE2 syntax for patterns like "(?i)error|panic". context_window returns surrounding lines after each match (lines sharing a context_window ID belong to the same match). Defaults to the last hour. If nothing comes back, widen the range or loosen the search — a container that just started may also not have shipped logs yet. Read-only. To wait for a line to APPEAR (readiness/migration-done markers like "database system is ready"), pass search plus wait_seconds: the call polls until the first match or the budget elapses, instead of you sleeping between calls. A no-match result after the wait is not failure — repeat the same call to keep waiting.
    ConnectorAPI key
  • FIND EVENT LOGS of a specific event on ONE Arbitrum (arb, ARB, Arbitrum One, L2) contract — "which X events involved contract Y, when, in which tx" in a single filtered query. Match by event NAME (e.g. "Transfer") or full SIGNATURE (e.g. "Transfer(address,address,uint256)"), case-insensitive. `contract` matches logs that contract EMITTED ITSELF (a proxy token is found by its public address), plus — when it is a proxy's implementation — the logs its code emitted for that proxy. Logs emitted by OTHER contracts it calls are NOT included: a DEX router's swaps are logged by the pair/pool it calls, not by the router, so contract=<router> with event=Swap returns NOTHING even when the router executed thousands of swaps. An empty result for a router, aggregator or smart wallet does NOT mean there was no activity. To get those logs, pass the pair/pool (or token) address as `contract`; if it is unknown, list the router's transactions with arbitrum_find_calls (contract=<router>) and pass their Tx hashes (up to 50, "|"-separated) to arbitrum_tx_events with event=Swap — its CallPath shows which call produced each log. Searches the LAST 7 DAYS by default — set after_time to widen or shift the window. Page back through history with cursor: pass the Cursor value of the LAST row of a page to get the next one — unlike before_time it never skips rows that share a timestamp, and a busy contract has hundreds of logs per second. The scan window follows the cursor, so every page covers the same span of days. Wide windows on very busy contracts can be slow — narrow the window or retry. For decoded asset movements use arbitrum_transfers_out / arbitrum_transfers_in; for the calls themselves use arbitrum_find_calls. Each row carries the log's decoded Arguments (Name, Type, Value, Indexed; integers are decimal strings in raw units, NOT divided by token decimals; addresses as 0x-hex) - at most 32 per row: ArgumentCount is the full number and ArgumentsTruncated=1 marks a cut list (every array element counts as one). Parsed=0 rows have no Arguments. Argument NAMES come from one known ABI for the Signature: a contract that emits the same Signature with other parameter names gets those names too, so a Name can be wrong for this contract - identify an argument by its position and Type, and check a doubtful one against the raw Topics/Data. For raw Topics/Data, or the rest of a cut list, pass the Tx to arbitrum_tx_events. Unrecognized events can be found here by `topic0`. ONE ROW = ONE EVENT LOG. A contract can be called many times inside a single transaction and each of those internal calls can emit its own logs, so the same event name legitimately repeats within one transaction - that is NOT duplication. Rows are told apart by CallIndex (which internal call emitted the log) together with LogInCall (the log's position inside that call); that pair is unique within a transaction. To COUNT events, count the returned rows - never de-duplicate on Tx/Event/Emitter, which would merge genuinely different logs into one. SCAN COST scales with the window, not with the limit: on a very high-traffic contract set days=1 and page back with cursor - several times cheaper than a 7-day window for the same page. Widen days for quiet contracts or rare matches. Rows inside one transaction come back in no particular order - sort them by CallIndex then LogInCall if you need emission order.
    ConnectorOAuth