OBSERVED DAILY FROM THE PUBLIC PRICING PAGE
タマワル
mcp · handle tamawaru · source page
Watch a series Current plans
Free tierFREE
Agent Free
Free
observed 5 days · last 2026-11-04
tamawaru|Agent Free|free|flat
ProMONTHLY
Agent Pro
$59/月 /mo
observed 5 days · last 2026-11-04
tamawaru|Agent Pro|pro|flat
Team / SMEMONTHLY
Agent Scale
$199/月 /mo
observed 5 days · last 2026-11-04
tamawaru|Agent Scale|team_sme|flat
IndividualMONTHLY
Agent Starter
$19/月 /mo
observed 5 days · last 2026-11-04
tamawaru|Agent Starter|individual|flat
Free tierFREE
Free
Free
observed 5 days · last 2026-11-04
fx_normalised: rate is stored in JPY; converted figures can wiggle a few cents day to day without a real repricing
tamawaru|Free|free|flat
ProMONTHLY
Light
¥4,980/月 /mo
observed 5 days · last 2026-11-04
string_rate_mismatch: page shows ¥4,980/月 but stored numeric rate is 31.44 JPY — display trusts the page string
fx_normalised: rate is stored in JPY; converted figures can wiggle a few cents day to day without a real repricing
tamawaru|Light|pro|flat
ProMONTHLY
Pro
¥39,800/月 /mo
observed 5 days · last 2026-11-04
string_rate_mismatch: page shows ¥39,800/月 but stored numeric rate is 251.26 JPY — display trusts the page string
fx_normalised: rate is stored in JPY; converted figures can wiggle a few cents day to day without a real repricing
tamawaru|Pro|pro|flat
ProMONTHLY
Standard
¥14,800/月 /mo
observed 5 days · last 2026-11-04
string_rate_mismatch: page shows ¥14,800/月 but stored numeric rate is 93.43 JPY — display trusts the page string
fx_normalised: rate is stored in JPY; converted figures can wiggle a few cents day to day without a real repricing
tamawaru|Standard|pro|flat
Direct accepted alternatives
localgov_jp_mcp_server · job 84%jGrants Util MCP Server · job 85%japan_admin_mcp · job 84%Japan Procurement MCP · job 76%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.
Inspect histories
Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.
This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series