← Back to search
Search • Sprawl Radar • TrustOps • Gateway • Ledger • Mandates • Hosting • Agent Commerce • Docs Compiler • Demo • Trust Index • Discovery Sources • Submit Repo • GitHub Action • Plans • Intelligence API • Verified Profiles • Shortlists • Rankings • Compare • Badges • Claim • ChatGPT compatible • Claude compatible • Healthcare • Digests • RSS • RSS XML • Backfill • MCP API
a-kabe-1qio/suguvisa-mcp

suguvisa-mcp

日本の特定技能ビザ申請を自動化するMCPサーバー。申請種別判定、必要書類リスト、期限計算、データ検証に対応。 **日本の特定技能（SSW）ビザ申請業務を、AIチャットだけで完結させる業界唯一のMCPサーバー。** 行政書士・登録支援機関・受入れ機関が日常的に行うビザ申請業務——申請種別の判定、必要書類の洗い出し、期限管理、書類生成——を **18種のAIツール** で自動化。Claude、ChatGPT、Cursor、Windsurf 等のAIアシスタントに直接組み込んで使えます。 ### ✨ できること - 🔍 **申請パターンの自動判定** — 「技能実習2号→特定技能1号」のように現在と申請先のビザを伝えるだけで、正式な申請種別・使用様式・標準処理期間・試験免除条件を瞬時に特定 - 📋 **必要書類リストの自動生成** — 130以上の申請パターンに対応。「2年以内の同一機関申請で省略可」「登録支援機関への委託で不要」等の省略条件を自動適用 - ⏰ **期限計算** — 随時届出の14日ルール、更新申請の3ヶ月前開始日、通算在留5年上限チェック、認定証明書の有効期限を自動算出し、リスクレベルを色分け警告 - 📸 **在留カードOCR** — Google Vertex AI Document AIによる高精度読み取り。氏名・国籍・在留資格・期限・カード番号を構造化データに変換（画像は保存しません） - 📄 **オンライン申請CSV/Excel生成** — 入管オンライン申請システムに直接アップロード可能な形式で一括出力。公式.xlsmテンプレートへのマクロ非破壊データ注入にも対応 - 📝 **紙申請PDFマッピング** — 紙申請書の全フィールドにデータを自動マッピングし、完成度をパーセント表示 - 📊 **年次定期届出の自動生成** — 受入れ状況・活動状況・支援実施状況をCSV（オンライン用）とExcel（紙提出用）で同時出力 - 🤖 **自律型ワークフロー** — AIが対話で不足データを収集し、判定→検証→書類生成まで自動実行。途中で人間の確認を挟むHITLパターン対応 - ⚖️ **法改正の自動追跡** — 制度変更・運用要領の改定を自動的に把握し、申請への影響を通知 - 🔎 **法務文書のAI検索** — Vertex AI Searchで法務マニュアル・チェックリスト・テンプレートを自然言語検索 - 📈 **申請結果の統計分析** — 補正率・通過率を申請パターンごとに集計し、次回申請の改善提案を自動生成 - 🔒 **監査ログ** — 全操作をSupabaseに記録し、コンプライアンスとトレーサビリティを確保

JSON report • Policy • Badge metadata • History API •
• Global feed
Decision: Block for production
Why: failing live status + score below evaluation threshold
Next: revalidate, add safeguards, export policy
EXECUTIVE VERDICT

Executive verdict

Production trust decision: Block for production
Reason: failing live status + score below evaluation threshold
Next action: revalidate, add safeguards, export policy
Production decision
Block for production
failing live status + score below evaluation threshold
Current score
45.1
Snapshot trustsnap_e9c921b1c25d08d5
Next action
revalidate, add safeguards, export policy
Claim the profile to add evidence, trigger validation, and configure monitoring.
Compare alternatives Export policy Open report JSON
Observed Attention
No observed attention
No observed attention in the current 30-day window.
  • No segmented attention signals observed in the current window.
Bucketed signal based on recent segmented Verify telemetry. Crawler and evaluator activity is not treated as confirmed human demand.
Evidence Tool risk Compatibility Policy History Badge Raw report
Status
Failing
Score
45.1
Transport
unknown
Tools
0

Current trust snapshot

Snapshot ID
trustsnap_e9c921b1c25d08d5
Use this ID to compare server page, report, policy, MCP, homepage, ranking, and shortlist surfaces.
Snapshot generated
Jul 09, 2026 02:22:05 AM UTC
All page, report, policy, and MCP surfaces use this same server-detail snapshot shape.
Last validated
Jul 08, 2026 10:32:55 PM UTC
Age: 3.82h • freshness band: Verified in last 24h • display score: 45.11
Production trust decision
Block for production
failing live status + score below evaluation threshold
Readiness class
unknown

Canonical machine links

Compare index
/compare.json
Compare API
/v1/compare?server=a-kabe-1qio%2Fsuguvisa-mcp
Trust summary
/v1/servers/a-kabe-1qio/suguvisa-mcp/trust-summary
Report JSON
/v1/servers/a-kabe-1qio/suguvisa-mcp/report
Policy export
/v1/servers/a-kabe-1qio/suguvisa-mcp/policy
Badge metadata
/v1/servers/a-kabe-1qio/suguvisa-mcp/badge
Ledger evidence
/v1/servers/a-kabe-1qio/suguvisa-mcp/ledger
Human compare URL
/compare?server=a-kabe-1qio%2Fsuguvisa-mcp
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/a-kabe-1qio/suguvisa-mcp/revalidate
Verified owners get priority queueing after proof succeeds.
3. Badge
Verified by MCP Verify badge
Verified by MCP Verify - score 45.1 - last checked Jul 8, 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/a-kabe-1qio/suguvisa-mcp.svg)](https://verify.sentinelsignal.io/servers/a-kabe-1qio/suguvisa-mcp)

MCP TrustOps

TrustOps turns this report into operational controls: freshness SLAs, authenticated validation, semantic benchmarks, policy exports, alert subscriptions, badges, cost/compliance metadata, and runtime routing. Fresh trusted index decisions stay separate from long-tail inventory so stale scores do not masquerade as current evidence.

Freshness band
Verified in last 24h
Policy SLA: 168.0h • confidence-weighted score: 22.6 • stale score suppressed: ✕
Policy exports
Export policy
Formats: json, rego, yaml, github_action, gateway_config, client_report
Runtime routing
/v1/decide
Returns allowed tools, blocked tools, approval requirement, and reason.
Hosted runtime
Verify Hosted MCP
Deploy trusted servers from GitHub with secrets, egress controls, releases, rollback, and audit events.
Authenticated validation
✕
Premium publisher feature: paid authenticated runs verify scopes, write-action safeguards, and authorized tool execution.
Active trust badges
Freshly Validated No Critical Risk
Semantic benchmarks
template ready
Templates cover GitHub, database, healthcare, web search, and CRM least-privilege jobs.
Supply chain
not scanned
Deep scan checks are marked separately from public metadata signals.
Compliance metadata
✕
Terms, privacy, SOC 2, HIPAA, GDPR, retention, deletion, and audit-log fields are tracked as enterprise metadata.
Alert subscription types
Status changes Score drops or recovers Freshness SLA breach Validation schema drift OAuth or auth behavior changes Tool surface changes New or changed write tool Supply-chain signal changes Legal or compliance metadata changes

MCP Runtime hosting

No hosted runtime profile is available yet.

Production readiness class

Production readiness class
Unknown
Fast server evidence is served while Verify protects web capacity.
Critical alerts
0
Production verdicts degrade quickly when critical alerts are active.

Evidence confidence

Confidence score
0.0
Full server evidence will be rebuilt by the regular cache refresh path.
Live checks captured
0
More direct checks increase trust in the current verdict.
Validation age
n/a
Lower age means fresher evidence.

Recommended for

No recommendation profile is available yet.

Client compatibility verdicts

No client compatibility verdicts are available yet.

Why compatibility is limited by client

No per-client remediation checklist is available yet.

Verdict traces

No verdict trace data is available yet.

Publishability policy profiles

No publishability policy profiles are available yet.

Compatibility fixtures

No compatibility fixtures are available yet.

Authenticated validation sessions

No authenticated validation detail is available yet.

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

Public server reputation

No public server reputation signals are available yet.

Incident & change feed

No incidents or changes recorded yet.

Capabilities

Use-case taxonomy
No taxonomy tags yet.

Security posture

No security posture summary available yet.

Agent Commerce & Payment Readiness - Beta

No agent-commerce assessment available yet.

Tool capability & risk inventory

No tool inventory available from the latest validation run.

Write-action governance

No write-action governance summary is available yet.

Action-controls diff

Need at least two validation runs before diffing action controls.

Why this score?

No score decomposition available yet.

Algorithmic score breakdown

Auth Operability
0/4
Measures whether auth discovery and protected access behave predictably for clients.
Error Contract Quality
0/4
Grades machine-readable error structure, status alignment, and remediation hints.
Rate-Limit Semantics
2/4
Checks whether quota/throttle responses are deterministic and automation-friendly.
Schema Completeness
0/4
Completeness of tool descriptions, parameter docs, examples, and schema shape.
Backward Compatibility
4/4
Stability score across tool schema/name drift relative to prior validations.
SLO Health
3/4
Availability, latency, and burst-failure profile across recent validation history.
Security Hygiene
1.5/4
HTTPS posture, endpoint hygiene, and response-surface hardening checks.
Task Success
1.7/4
Can an agent reliably initialize, enumerate tools, and execute core MCP flows?
Trust Confidence
2/4
Confidence-adjusted reliability score that penalizes low evidence volume.
Abuse/Noise Resilience
3/4
How well the server preserves core behavior in the presence of noisy traffic patterns.
Prompt Contract
2/4
Quality of prompt metadata, argument shape, and prompt discoverability for clients.
Resource Contract
2/4
How completely resources and resource templates describe URIs, types, and usage shape.
Discovery Metadata
3/4
Homepage, docs, icon, repository, support, and license coverage for directory consumers.
Registry Consistency
2/4
Agreement between stored registry metadata, live server-card data, and current validation output.
Installability
2/4
How cleanly a real client can connect, initialize, enumerate tools, and proceed through auth.
Session Semantics
0/4
Determinism and state behavior across repeated MCP calls, including sticky-session surprises.
Tool Surface Design
0/4
Naming clarity, schema ergonomics, and parameter complexity across the tool surface.
Result Shape Stability
0/4
Stability of declared output schemas across validations, with penalties for drift or missing shapes.
OAuth Interop
0/4
Depth and client compatibility of OAuth/OIDC metadata beyond the minimal protected-resource check.
Recovery Semantics
0/4
Whether failures include actionable machine-readable next steps such as retry or upgrade guidance.
Maintenance Signal
3.8/4
Versioning, update recency, and historical validation cadence that indicate active stewardship.
Adoption Signal
2/4
Directory presence and distribution clues that suggest the server is intended for external use.
Freshness Confidence
3/4
Confidence that recent validations are current enough and dense enough to trust operationally.
Transport Fidelity
0/4
Whether declared transport metadata matches the observed endpoint behavior and response formats.
Spec Recency
2/4
How close the server’s claimed MCP protocol version is to the latest known public revision.
Session Resume
0/4
Whether Streamable HTTP session identifiers and resumed requests behave cleanly for real clients.
Step-Up Auth
3/4
Whether OAuth metadata and WWW-Authenticate challenges support granular, incremental consent instead of broad upfront scopes.
Transport Compliance
1/4
Checks session headers, protocol-version enforcement, session teardown, and expired-session behavior.
Utility Coverage
2/4
Signals support for completions, pagination, and task-oriented utility surfaces that larger clients increasingly expect.
Advanced Capability Coverage
2/4
Coverage of newer MCP surfaces like roots, sampling, elicitation, structured output, and related metadata.
Connector Publishability
0/4
How ready the server looks for client catalogs and managed connector programs.
Tool Snapshot Churn
0/4
Stability of the tool surface across recent validations, including add/remove and output-shape drift.
Connector Replay
3/4
Whether a previously published frozen connector snapshot would remain backward compatible after the latest tool refresh.
Request Association
3/4
Whether roots, sampling, and elicitation appear tied to active client requests instead of arriving unsolicited on idle sessions.
Interactive Flow Safety
3/4
Whether prompts and docs steer users toward safe auth flows instead of pasting secrets directly.
Action Safety
3/4
Risk-weighted view of destructive, exec, egress, and confirmation semantics across the tool surface.
Official Registry Presence
3/4
Whether the server appears directly or indirectly in the official MCP registry.
Provenance Divergence
4/4
How closely official registry metadata, the live server card, and public repo/package signals agree with each other.
Safety Transparency
4/4
Clarity of docs, auth disclosure, support links, and other trust signals visible to integrators.
Tool Capability Clarity
0/4
How clearly the tool surface communicates whether each action reads, writes, deletes, executes, or exports data.
Destructive Operation Safety
3/4
Penalizes delete/revoke/destroy style tools unless auth and safeguards reduce blast radius.
Egress / SSRF Resilience
3/4
Assesses arbitrary URL fetch, crawl, webhook, and remote-request exposure on the tool surface.
Execution / Sandbox Safety
4/4
Evaluates shell, code, script, and command-execution exposure and whether that surface appears contained.
Data Exfiltration Resilience
3/4
Assesses export, dump, backup, and bulk-read behavior against the surrounding auth and safeguard signals.
Least Privilege Scope
2/4
Rewards scoped auth metadata and penalizes broad or missing scopes around privileged tools.
Secret Handling Hygiene
3/4
Assesses secret-bearing tools, token leakage risk, and whether the public surface avoids obvious secret exposure.
Supply Chain Signal
0.5/4
Public metadata signal for repository, changelog, license, versioning, and recency that supports supply-chain trust.
Input Sanitization Safety
0/4
Penalizes risky freeform string inputs when schemas do not constrain URLs, code, paths, queries, or templates.
Tool Namespace Clarity
0/4
Measures naming uniqueness and ambiguity across the tool namespace to reduce collision and confusion risk.

Compatibility profiles

No compatibility profiles available.

Actionable remediation

No remediation items. Current evidence does not show urgent client-facing fixes.

Point loss breakdown

No current score penalties are recorded.

Validation diff

Need at least two validation runs before diffing changes.

Tool snapshot diff & changelog

Need at least two validation runs before building a tool changelog.

Connector replay

No connector replay evidence is available yet.

Transport compliance drilldown

No transport compliance drilldown is available yet.

Request association

No request-association evidence is available yet.

Utility coverage

No utility-coverage summary is available yet.

Benchmark tasks

No benchmark tasks are available yet.

Registry & provenance divergence

No provenance-divergence summary is available yet.

Active alerts

No active alerts for the current server state.

Aliases & registry graph

No aliases discovered for this server.

Alias consolidation

No alias consolidation details are available yet.

Install snippets

No install snippets available.

Agent access & tool surface

Live server tools
No live tool surface captured yet.
Observed from the latest live validation against none. This is the target server surface, not Verify's own inspection tools.
Live capability counts
0 tools • 0 prompts • 0 resources
Counts come from the latest tools/list, prompts/list, and resources/list checks.
Inspect with Verify
search fetch search_servers recommend_servers get_server_report compare_servers
Use Verify itself to search, recommend, compare, and fetch the full report for a-kabe-1qio/suguvisa-mcp.
Direct machine links
JSON report • Compare this server • Verify MCP API

Claims & monitoring

Server ownership

No verified maintainer claim recorded.

Watch subscriptions
0
Teams: none

Alert routing

No alert routing is configured yet.

Maintainer analytics

No maintainer analytics available.

Maintainer response quality

No maintainer response quality signals are available yet.

Maintainer annotations

No maintainer annotations have been recorded yet.

Maintainer rebuttals & expected behavior

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

Latest validation evidence

No validation run available yet.

Raw evidence view

No raw evidence recorded.

Known versions

Validation history

No historical trend summary is available yet.

Validation timeline

No validation timeline is available yet.

Recent validation runs

StartedStatusSummaryLatencyChecks
No validation runs yet.