Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.branpastran/project-little-weirdo

REMOTE · WEIRDO-GENESIS-WATCH.LOVABLE.APP

Deterministic public-web change observation with evidence-bound commercial interpretation.

0 this week 85 Trust /100

Last scanned (2 hours ago)

Scores higher than 92% of remote servers

Reachable. Last reached 17 Oct 2026.

Category Search and Retrieval

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 548 tokens (~274/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 9 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Aug 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 17 Oct 2026 · Probed https://weirdo-genesis-watch.lovable.app/api/public/weirdo/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=lovable.app CN=WE1,O=Google Trust Services,C=US 10 Oct 2026 9 Jan 2027 ECDSA 256 ECDSA-SHA256 a0305f14b2a99af130a9e43af07d3e5
SANs: lovable.app, *.lovable.app
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of weirdo-genesis-watch.lovable.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
lovable.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://weirdo-genesis-watch.lovable.app/api/public/weirdo/v1/mcp Verified 200
http (plaintext) http://weirdo-genesis-watch.lovable.app/api/public/weirdo/v1/mcp HTTPS enforced 301 https://weirdo-genesis-watch.lovable.app/api/public/weirdo/v1/mcp
MCP tools · 2 exposed · ~382 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
interpret_commercial_change ~215

SEMANTIC INTERPRETATION over PRICING AND COMMERCIAL-OFFER PAGES ONLY. Requires a target that already has two persisted observations with a deterministic CONTENT_CHANGED verdict; it never refetches the page and never decides whether a change occurred. Input: targetId (returned by observe_public_page), optionally fromObservationId/toObservationId. Returns classified commercial changes (price, plan, discount, availability, packaging...) where every claim quotes observed before/after text, plus rejected claims and their rejection reasons. Uncertainty: unsupported, immaterial, numerically inconsistent or low-confidence claims are discarded. Non-commercial pages return INSUFFICIENT_EVIDENCE with no changes. There is no guarantee that a page contains commercial intelligence. Cost: free beta, model-backed and separately rate limited per credential.

NameTypeReqDescription
fromObservationIdstring–Optional 'before' observation UUID.
targetIdstringyesTarget UUID from a previous observation.
toObservationIdstring–Optional 'after' observation UUID.

No output schema declared.

No examples provided.

observe_public_page ~167

DETERMINISTIC OBSERVATION. Fetches one lawful public web page and records a bounded representation of it (title, normalized text length, content fingerprint). If the page was observed before, returns an arithmetic comparison against the previous observation: BASELINE_CREATED, NO_CHANGE or CONTENT_CHANGED. Makes no claim about meaning. Input: url (public http/https page). Private, loopback and internal addresses are refused; redirects, response size and timeouts are bounded. Uncertainty: the verdict is arithmetic, not semantic. A CONTENT_CHANGED verdict proves the content differs, not that the difference matters. Cost: free beta, rate limited per credential. No payment capability exists.

NameTypeReqDescription
urlstringyesAbsolute http(s) URL of a lawful, public, non-credentialed page.

No output schema declared.

No examples provided.

Install

How do I install the io.github.branpastran/project-little-weirdo MCP server?

io.github.branpastran/project-little-weirdo is a hosted endpoint at https://weirdo-genesis-watch.lovable.app/api/public/weirdo/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · weirdo-genesis-watch.lovable.app

# add to Claude Code
claude mcp add --transport http branpastran-project-little-weirdo 'https://weirdo-genesis-watch.lovable.app/api/public/weirdo/v1/mcp'
Common questions

What is the io.github.branpastran/project-little-weirdo MCP server?

io.github.branpastran/project-little-weirdo is an MCP server listed in the public MCP registry as io.github.branpastran/project-little-weirdo. Deterministic public-web change observation with evidence-bound commercial interpretation. This page covers its hosted endpoint (https://weirdo-genesis-watch.lovable.app/api/public/weirdo/v1/mcp).

Is the io.github.branpastran/project-little-weirdo MCP server safe to use?

io.github.branpastran/project-little-weirdo scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.branpastran/project-little-weirdo MCP server expose?

io.github.branpastran/project-little-weirdo exposes 2 tools: observe_public_page, interpret_commercial_change. Their descriptions and schemas cost roughly 382 tokens of context every time the server is loaded.

Does the io.github.branpastran/project-little-weirdo MCP server require authentication?

No. We connected to io.github.branpastran/project-little-weirdo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.branpastran/project-little-weirdo MCP server still maintained?

io.github.branpastran/project-little-weirdo is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.