Search • Rankings • TrustOps • Docs • Pricing • Claim/Manage

MAINTAINER CONTROL PLANE

ncosic/webotee-mcp

Claim ownership, trigger a revalidation, update metadata, and inspect exactly where points are being lost.

github-ncosic/webotee-mcp

Owner funnel

Claim, verify ownership, revalidate, add evidence, publish badges, and configure monitoring from this maintainer control plane.

Current deployment

This page is no-store and rendered with MCP Verify v1.0.508.

SERVER OWNER FUNNEL

Own this MCP?

Claim ownership, prove control with a GitHub, DNS, HTTP, MCP metadata, or email-domain challenge, revalidate now, publish a badge, configure monitoring, and unlock a verified server profile.

1. Claim

unclaimed

with GitHub, DNS, or HTTP challenge instructions.

2. Revalidate

POST /v1/servers/github-ncosic/webotee-mcp/revalidate

Verified owners get priority queueing after proof succeeds.

3. Badge

Verified by MCP Verify - score n/a - last checked Aug 5, 2026

4. Monitor

Continuous Verify plan is self-serve: choose a tier, configure watches, add authenticated validation, trigger revalidation, and use the badge.

Paid profile

Verified Server Profile

Add verified publisher identity, security metadata, evidence packs, badge customization, and owner analytics without buying a better score.

Badge embed

[![Verified by MCP Verify](https://verify.sentinelsignal.io/badge/github-ncosic/webotee-mcp.svg)](https://verify.sentinelsignal.io/servers/github-ncosic/webotee-mcp)

PUBLISHER READINESS

Publisher readiness checklist

1/7 readiness checks currently pass. Paid status never changes the objective score; it can add evidence, monitoring, badge analytics, and authenticated validation.

Publisher readiness checks for this MCP server
Check	Status	How to improve
Ownership verified	Needs work	Prove GitHub, DNS, HTTP, MCP metadata, or domain-email control.
Recent validation (48h)	Ready	Keep public evidence inside the 48h publisher launch window.
Healthy endpoint	Needs work	Remote endpoint should initialize and list tools reliably.
Score threshold	Needs work	Aim for score >= 70 before using production-readiness language.
Metadata complete	Needs work	Publish description, homepage/docs, remote URL, and support metadata.
Risk posture reviewed	Needs work	Address OAuth, write-action, destructive-tool, and protocol findings.
Badge ready	Needs work	Publish score and freshness badges only when current evidence exists.

Scan or claim this server Open badge kit

Where points are being lost

No current score penalties are recorded.

LOW-FRICTION CLAIM INTENT

Own this server?

Enter a GitHub handle, GitHub repo, or email to receive claim instructions. This records owner intent before the full GitHub, DNS, HTTP, or MCP metadata challenge.

Claim server

Owner name Organization Contact email Proof URL

For HTTP file, use the public text-file URL, for example https://www.webotee.com/.well-known/mcp-verify-claim.txt, not the MCP JSON-RPC endpoint.

Challenge type

HTTP file: publish mcp-verify-claim=<token> at a public .well-known URL on an allowed server domain.

Create a claim to get your Claim ID, verification token, and exact proof instructions.

Claim ID Verification token Proof URL or DNS name

After publishing the proof token, click Verify claim.

Claims & monitoring

Server ownership

No verified maintainer claim recorded.

Watch subscriptions

Teams: none

Revalidate now

Verification token Reason

Queue a validation job for this server. Verified maintainers get higher priority; unclaimed public requests are accepted at normal priority.

Maintainer analytics

No maintainer analytics available.

Maintainer response quality

No maintainer response quality signals are available yet.

Update metadata

Verification token

Title Homepage URL Docs URL Support URL

Description Icon URL Server card URL

Save title, description, links, icon, and server-card metadata. Requires a verified maintainer token and queues a revalidation after changes are recorded.

Maintainer annotations

No maintainer annotations have been recorded yet.

Attach changelog links, incident notes, support links, or explicit tool-change notes so Verify can show maintainer context next to live probes.

Verification token

Annotation type Title URL

Applies to Notes

Add maintainer context such as changelog, incident, migration, or expected-behavior notes. Requires a verified maintainer token.

Maintainer rebuttal

No maintainer rebuttals or expected-behavior overrides are recorded yet.

Submit context for a specific failed or disputed check. Rebuttals are score-neutral and enter operator triage before they are shown as accepted context.

Verification token

Check ID Title Evidence URL

Explanation

Verified maintainers can submit rebuttals. Operators triage these before they affect public context; they never directly alter the score.

Alert routing

No alert routing is configured yet.

Continuous Verify plan

Production publisher setup: claim server, verify ownership, start Stripe Checkout, get a badge, configure alerts, trigger revalidation, and track usage through the API response. Paid features activate only after Stripe confirms the subscription webhook.

Verified claim token Plan Billing contact

Start Stripe Checkout for this claimed server. Paid status unlocks workflow features only after webhook-confirmed payment, and never changes the objective trust score.

Alert contact Watch label Minimum severity

Create an active watch subscription for score, status, freshness, write-surface, and registry-drift changes. Enter an alert email before saving.

Badge

Verified publishers can embed the live score and trust badges after claim verification.

[![Verified by MCP Verify](https://verify.sentinelsignal.io/badge/github-ncosic/webotee-mcp.svg)](https://verify.sentinelsignal.io/servers/github-ncosic/webotee-mcp)

Copy Markdown for your README or docs. Badge traffic links back to the public Verify profile and does not affect score.

Premium authenticated validation

Public validation is free. Authenticated validation is paid and proves scoped behavior, write-action safeguards, and authenticated tool execution.

Verified claim token Credential label

The label is only a name for this saved test session. It is not the secret used for authentication.

Credential type

Bearer token: paste a non-production test access token. Verify sends it as Authorization: Bearer <token> during authenticated validation.

Bearer token value

Schedule interval hours

Store test-session credentials in the encrypted vault and schedule authenticated validation. Requires a verified claim and a plan with authenticated validation enabled.

API responses

No request submitted yet.