UCP conformance score, top priorities, impact & effort matrix, and copy-paste fixes for every issue.
easytax.biz publishes a conforming profile with broad capability coverage.
Agent Discovery is solid (100/100).
Fix broken spec or schema URLs → Publish the public keys agents use to check your messages → Move to the latest UCP protocol version
One or more spec/schema URLs declared in the profile do not resolve.
Your UCP profile lists no public keys, so an agent cannot confirm that a message really came from your store.
Your profile declares a valid but older protocol version. A newer one is published.
Prioritised recommendations by expected impact and implementation effort
High impact, low effort
High impact, high effort
Medium impact & effort
Lower priority
Response time benchmarked against 7,457 Wixes we monitor.
All improvements ranked by priority, with evidence and actionable fixes.
One or more spec/schema URLs declared in the profile do not resolve.
Spec and schema URLs let agents validate request/response shapes before sending. When they 404 or time out, runtime validation degrades to "best effort" and strict agents reject the integration entirely. Common cause: copy-pasting a placeholder URL during initial profile setup. See the Full Check Breakdown for the specific URLs that failed.
Your UCP profile lists no public keys, so an agent cannot confirm that a message really came from your store.
Agents use these keys to check that checkout messages really came from you. A store that takes payment through the agent needs them. A store that sends the buyer to its own checkout page can manage without them for now.
Create an Ed25519 key pair. Add the public key to a "keys" list at the top level of your UCP profile, as in the example, and keep the private key on your server. Replace the key once a year, giving each new key its own "kid".
{
"keys": [
{
"kty": "OKP",
"crv": "Ed25519",
"x": "<base64url-encoded-public-key>",
"kid": "key-2026-04",
"alg": "EdDSA"
}
],
"ucp": { ... }
}Your profile declares a valid but older protocol version. A newer one is published.
Older versions stay valid (agents use the version you declare), but newer abilities (embedded checkout, agent payment mandates, linked customer accounts, card authentication, payment terms and store location lookup) only work against the latest version. The profile itself barely changes: the signing keys move to a root-level "keys" list, and the rest of the update is in what capabilities can say.
Set the version to 2026-08-25 and publish your public keys as a root-level "keys" list. The older "signing_keys" field is still accepted, but "keys" is the one every verifier reads.
"ucp": {
"version": "2026-08-25",
...
},
"keys": [ ... ] // beside "ucp", not inside itEvery signal we evaluate, grouped by category.
Can AI agents find your store and its UCP profile?
Profile served over a secure connection.
Profile URL uses https://
Agents reject non-HTTPS endpoints outright. Signed payloads over HTTP are meaningless because the channel itself is tamperable.
Profile fetched OK from /.well-known/ucp.
HTTP 200
Agents start every session by fetching this URL. If it 404s or times out, the store is invisible to agent commerce.
robots.txt allows agent crawlers to fetch the profile.
robots.txt allows /.well-known/ucp
Agents respect robots.txt. Even a published profile gets ignored if the file is disallowed for known agent user-agents.
Hand-written brief at /llms.txt for AI agents.
Found at /llms.txt
Emerging convention (analogous to robots.txt). Recommendation/discovery agents read it for brand context, return policy, and crawl preferences.
XML sitemap published at /sitemap.xml.
Found at /sitemap.xml
Tells agents which pages are canonical and how often they change. Without it, agents fall back to following internal links.
OG meta tags on the homepage.
og:title and og:type/url present
OG tags drive how your store unfurls in agent surfaces, Slack, iMessage, and ChatGPT shares.
Schema.org Organization (or OnlineStore) JSON-LD on homepage.
Organization-typed JSON-LD detected
Gives agents a structured representation of your brand identity — used to verify you are who your profile claims you are.
Viewport meta tag for mobile rendering.
<meta name="viewport"> present
Mobile agent sessions render in browser sandboxes that respect this. Without it, screenshots taken by agents are unreadable.
Does your profile meet the published spec?
Profile structure conforms to the published UCP spec.
No structural errors
Strict UCP agents reject profiles with structural errors. The error code in the diagnostic shows which field failed.
ucp.version follows YYYY-MM-DD format.
Version: 2026-04-08
UCP versions are dates, not semver. Agents pick the closest matching schema based on this string.
Root-level keys array (canonical since 2026-07-12; legacy signing_keys also accepted) for response verification.
No signing_keys at root (common for managed/redirect-checkout stores)
Required for tokenized payment flows in v2026-04-08+. Stores using checkout-link redirects (e.g. WooCommerce native) often skip this safely.
Profile passes structural and field-level rules.
1 warning
Each warning is a strict-spec deviation — the recommendations section above lists them with copy-code fixes.
Resolves the 12 spec/schema URLs declared across the profile to confirm agents can fetch each one.
Did not resolve (6 of 12): https://ucp.dev/services/shopping/rest.openapi.json, https://ucp.dev/schemas/shopping/cart.json, https://ucp.dev/schemas/shopping/catalog-lookup.json, https://ucp.dev/schemas/shopping/checkout.json, https://ucp.dev/schemas/shopping/fulfillment.json, …
Spec and schema URLs let agents validate request/response shapes before sending. Broken URLs degrade runtime validation to "best effort" and cause strict agents to refuse the capability entirely.
What operations can agents actually perform?
Number of agent-readable capabilities under ucp.capabilities.
3 of 6 capability families detected: Checkout, Cart Management, Catalog. A family counts once however many namespaces or extensions declare it.
Capabilities tell agents what operations to attempt. More coverage = more sessions complete end-to-end without falling back to scraping.
Store declares a checkout-namespaced capability.
dev.ucp.shopping.checkout detected
Without a checkout capability, agents can browse but can't complete a purchase end-to-end.
Service transports (REST/MCP/A2A/Embedded) declared on services.
REST, MCP
Transports tell agents how to actually call your endpoints. MCP and REST are the most widely supported today.
Tokenized payment handlers registered for in-conversation checkout.
Empty array: checkout-link redirect strategy
Tokenized payment lets agents complete purchases without redirecting the buyer to a hosted checkout. Empty by design is valid for WooCommerce-style native checkouts.
Live reachability check against https://www.wixapis.com/ecom/ucp/09eda594-f0b6-44ec-b711-ac1fe52fe89e.
Host responded with HTTP 404 — endpoint reachable but path may be method-restricted
A declared transport that does not respond means agents will hit a dead end the moment they try to use the capability — even if the profile itself looks perfect.
Live reachability check against https://www.wixapis.com/ecom/ucp/09eda594-f0b6-44ec-b711-ac1fe52fe89e/mcp.
tools/list returned a JSON-RPC response in 145ms
A declared transport that does not respond means agents will hit a dead end the moment they try to use the capability — even if the profile itself looks perfect.
The plain-text brief this store publishes to AI agents. Captured on the most recent check.
# 편리한택스
> 이 웹사이트는 사업자를 위한 세무 및 경영 컨설팅 서비스를 제공합니다. 세금, 노무, 대출, 지원금 등 사업 운영 전반의 복잡한 문제들을 처리하여 사업주가 본업에 집중할 수 있도록 돕습니다. 다양한 업종의 고객 후기를 통해 전문성과 편리성을 강조하며, 사업장 기장, 세금 신고 대행, 기업진단보고서 작성, 재산 관련 상담 등 폭넓은 서비스를 제공합니다. 이를 통해 사업장의 세금 관련 걱정을 덜어주고 효율적인 경영을 지원하는 것을 목표로 합니다.
## Homepage link
- [home](https://www.easytax.biz/)
## AI 에이전트 액세스
본 사이트는 Wix 기반으로 하며 에이전트 AI 액세스를 위한 Model Context Protocol(MCP)을 지원합니다. AI 에이전트가 라이브, 최신 사이트 콘텐츠에
직접 연결하여 가져올 수 있으며 스크래핑이 필요 없습니다.
- [**사이트 MCP 엔드포인트**](https://www.easytax.biz/_api/mcp)
- [**Wix MCP 문서**](https://dev.wix.com/docs/develop-websites/articles/get-started/about-the-wix-site-mcp)
## 이용 가능한 MCP 도구
### GetBusinessDetails
시간대, 이메일, 전화, 주소 등 비즈니스 및 사이트 정보를 불러옵니다.
- 파라미터가 필요하지 않습니다.
### SearchInSite
사이트에서 정보를 검색합니다.
- **searchTerm** - 사이트에서 검색할 용어.
### SearchSiteApiDocs
본 사이트에 설치된 Wix 비즈니스 솔루션의 API 문서를 불러오고, AI 클라이언트에게 API 사용 방법을 안내합니다. (SearchInSite 대신)
제품 및 서비스를 쿼리할 때 해당 도구를 사용하세요.
- **searchTerm** - 사이트 API 문서에서 검색할 용어.
### GenerateVisitorToken
새 방문자 세션을 생성하고 사이트의 방문자 액세스 토큰을 얻습니다.
컨텍스트에 방문자 토큰이 없는 경우
CallWixSiteAPI 요청을 하기 전에 호출해야 합니다.
- 파라미터가 필요하지 않습니다.
### CallWixSiteAPI
사이트에서 API 메서드를 호출하여 방문자를 대신하여 사이트 데이터 쿼리,
일대일 세션 예약, 구매 시작 등의 작업을 수행합니다.
- **visitorToken** - 방문자 액세스 토큰. 사용할 수 없는 경우 GenerateVisitorToken을 먼저 사용하세요.
- **url** - 호출할 API 메서드의 절대 URL(예: https://www.wixapis.com/...). SearchSiteApiDocs를 사용하여 불러오세요.
- **method** - API 호출에 사용할 HTTP 메서드.
- **body** - 유효한 JSON 문자열 형식의 요청 본문.
### ReadFullDocsArticle
Wix 개발자 문서 포털에서 전체 문서를 가져옵니다.
- **articleUrl** - Wix 개발자 문서 포털에 있는 문서의 URL.
### ReadFullDocsMethodSchema
Wix API 메서드의 전체 스키마를 가져옵니다. CallWixSiteAPI를 통해
실제 메서드를 호출하기 전에 호출되어야 합니다.
- **articleUrl** - Wix API 메서드에 대한 참조 문서의 URL.
## AI + MCP를 통해 방문자가 할 수 있는 작업
- 비즈니스 정보 가져오기(연락처 정보, 위치, 영업시간)
- 제공되는 제품 및 서비스 둘러보기
- 서비스 예약 및 예매
- 구매 시작 및 사이트에서 체크아웃 완료
- 사이트를 검색하지 않고 질문하고 관련 답변 받기
## 참고 사항
- MCP 엔드포인트에 연결하는 데 인증이 필요하지 않습니다.
- 사이트에서 접근 가능한 공개 정보만 이용 가능합니다.
- 콘텐츠는 항상 실시간으로 최신 상태로 유지됩니다.
- 도구 업데이트를 받으려면 도구 업데이트 알림 수신 시 tools/list 호출을 구현하세요.| Cart ✓ Bound | 2026-04-08 |
| Checkout ✓ Bound | 2026-04-08 |
| Fulfillment Extension ✓ Bound | 2026-04-08 |
| Catalog Lookup ✓ Bound | 2026-04-08 |
| Catalog Search ✓ Bound | 2026-04-08 |
| UCP Status | Verified |
| Endpoint | https://easytax.biz/.well-known/ucp |
| HTTP Status | 200 |
| UCP Version | 2026-04-08 |
| Transports | REST, MCP |
| Last Observed | |
| Last Full Index |
Drop the live grade into your README, status page, or marketing site. The badge auto-updates as your score changes.
Live preview[](https://ucpchecker.com/score/easytax.biz)<a href="https://ucpchecker.com/score/easytax.biz"><img src="https://ucpchecker.com/score/easytax.biz/badge.svg" alt="UCP Score for easytax.biz"></a>This score reflects data from the most recent crawl. Run a fresh check to update, or read the methodology to see how each signal is scored.
Track easytax.biz's UCP score over time. We'll re-run the full check weekly and email you if the score drops, a capability regresses, or status flips.
Free. One email when something changes — no marketing. Privacy.
Track domains and get emailed when their UCP status changes.
By continuing you agree to our Terms & Privacy Policy.