Question 1

What is WebMCP?

Accepted Answer

WebMCP is an evolving browser API proposal that lets a web application expose JavaScript-backed tools to compatible agents through the page's model context.

Question 2

Is WebMCP the same thing as MCP?

Accepted Answer

No. MCP is the broader client-server protocol ecosystem. WebMCP brings a related tool model into a web page's client-side application context.

Question 3

Is WebMCP a W3C Standard?

Accepted Answer

No. As of August 31, 2026, it is a Web Machine Learning Community Group report and is not on the W3C Standards Track.

Question 4

Does every browser support WebMCP?

Accepted Answer

No. Feature-detect the API, test in the browser and agent environments you support, and keep the application usable when WebMCP is absent.

Question 5

Does WebMCP replace my accessible UI or backend APIs?

Accepted Answer

No. The visible UI should remain complete and accessible, while WebMCP handlers normally reuse the same services, authorization, and business rules.

Question 6

What is imperative versus declarative WebMCP?

Accepted Answer

Imperative WebMCP registers JavaScript tool objects. The current draft's declarative execution model remains unfinished, so guidance must be date-stamped against the latest draft.

Question 7

What belongs in a WebMCP tool contract?

Accepted Answer

At minimum: a stable name, precise description, narrow input schema when needed, execution handler, and accurate annotations.

Question 8

What makes a good first WebMCP tool?

Accepted Answer

Choose a narrow, well-understood action with few inputs, a clear result, and preferably read-only or easily reversible effects.

Question 9

Should UI and WebMCP handlers use the same code?

Accepted Answer

They should be adapters over the same application or domain service so permissions, validation, persistence, and outcome semantics cannot drift.

Question 10

How do I remove tools when a route changes?

Accepted Answer

Pass an AbortSignal when registering route-scoped tools and abort the owning controller during cleanup.

Question 11

Can a tool exist without changing the visible page?

Accepted Answer

Yes for read-only content or background operations, but any page state it does change should stay synchronized and inspectable.

Question 12

How long should a tool description be?

Accepted Answer

Keep it concise enough to describe when to use the tool, its material effect, and an important boundary. Do not include dynamic content or persuasion.

Question 13

Will WebMCP always save tokens, time, or money?

Accepted Answer

No. Outcomes depend on the task, contract, agent, browser, and implementation. Measure equivalent completed journeys instead of publishing a universal savings claim.

Question 14

How do I know a tool actually succeeded?

Accepted Answer

Verify observable postconditions such as a stable record ID, authoritative state change, or synchronized UI rather than trusting a success string.

Question 15

Is successful registration a conformance test?

Accepted Answer

No. Registration proves presence in one runtime. It does not prove selection, authorization, lifecycle cleanup, state accuracy, or task success.

Question 16

What should a selection eval include?

Accepted Answer

Use fixed positive, negative, ambiguous, and near-miss prompts against a versioned tool inventory, then report false positives and misses across repeated trials.

Question 17

What can isWebMCP Quick Scan prove?

Accepted Answer

It reports Source Actionability from a bounded window of public HTML. It does not execute target JavaScript, authenticate, or certify runtime WebMCP behavior.

Question 18

Does importing a manifest prove implementation?

Accepted Answer

No. Contract Lint reviews bounded user-supplied definitions with unverified provenance; it is not independent Runtime Readiness evidence.

Question 19

How should I read the isWebMCP evidence layers?

Accepted Answer

Source Actionability covers captured HTML, Contract Lint covers sanitized imported definitions, and Runtime Readiness requires observed trials. WebMCP Lift is separate: it is available only for paired interactive runs, never authored replay.

Question 20

Is an input schema enough to make a tool safe?

Accepted Answer

No. The implementation still needs validation, authorization, limits, business-rule checks, cancellation, and safe error handling.

Question 21

How should authentication and authorization work?

Accepted Answer

Treat every tool call as untrusted input and enforce identity, tenant, object, role, and business rules in the same trusted layer used by the UI.

Question 22

How should tools expose state-changing actions?

Accepted Answer

Use unambiguous names, disclose material effects, preserve appropriate confirmation, consider idempotency, and return verification evidence.

Question 23

How much user data should a tool request?

Accepted Answer

Only fields required for the declared action. Avoid speculative personalization, duplicate identity data, and unconstrained free text.

Question 24

Does WebMCP eliminate prompt injection?

Accepted Answer

No. Metadata and returned content can become attack surfaces, so mitigation requires layered application, browser, agent, and evaluation controls.

Question 25

What does untrustedContentHint do?

Accepted Answer

It signals that a result includes untrusted material. It can inform downstream policy, but it is not a sanitizer or complete defense.

Question 26

Are Devpost participants the same as submissions?

Accepted Answer

No. The participant counter reflects registrations, while submitted projects appear in the project gallery. isWebMCP never infers one from the other.

Question 27

Can isWebMCP list participant identities?

Accepted Answer

The public participants page currently requires login to browse identities. The tracker records only public aggregate observations and does not bypass that boundary.

Question 28

What does the WebMCP Challenge require?

Accepted Answer

The current FAQ lists a working hosted project, project description, public licensed source repository, and a short demo video. Verify the live rules before submission.

Question 29

When is the current submission deadline?

Accepted Answer

Devpost currently lists September 3, 2026 at 1:00 PM Pacific. Use the live challenge page as the authority.

Question 30

Should the site keep deploying during judging?

Accepted Answer

No. The current challenge FAQ says to stop editing the submission, repository, and live site after the deadline until winners are announced.

The questions people ask before they ship.

Fundamentals

Building

Testing

Security

Challenge

Move from the answer to the implementation.